[ << ] [ >> ]           [] [] [] [ ? ]

11 Amiga output module

This chapter describes the AmigaOS hunk-format output module which can be selected with the ‘-Fhunk’ option to generate objects and with the ‘-Fhunkexe’ option to generate executable files.

11.1 Legal

This module is written in 2002-2016 by Frank Wille and is covered by the vasm copyright without modifications.

11.2 Additional options for this version


Use only those hunk types and external reference types which have been valid at the time of Kickstart 1.x for compatibility with old assembler sources and old linkers. For example: no longer differentiate between absolute and relative references. In executables it will prevent the assembler from using 16-bit relocation offsets in hunks and rejects 32-bit PC-relative relocations.


Automatically generate an SAS/C-compatible LINE DEBUG hunk for the input source. Overrides any line debugging directives from the source.


Do not delete empty sections without any symbol definition.

These options are valid for the hunkexe module only:


Try to shorten sections in the output file by removing zero words without relocation from the end. This technique is only supported by AmigaOS 2.0 and higher.

11.3 General

This output module outputs the hunk object (standard for M68k and extended for PowerPC) and hunkexe executable format, which is a proprietary file format used by AmigaOS and WarpOS.

The hunkexe module will generate directly executable files, without the need for another linker run. But you have to make sure that there are no undefined symbols, common symbols, or unusual relocations (e.g. small data) left.

It is allowed to define sections with the same name but different attributes. They will be regarded as different entities.

11.4 Restrictions

The hunk/hunkexe output format is only intended for M68k and PowerPC cpu modules and will abort when used otherwise.

The hunk module supports the following relocation types:

The hunkexe module supports absolute 32-bit relocations only.

11.5 Known Problems

Some known problems of this module at the moment:

11.6 Error Messages

This module has the following error messages:

[ << ] [ >> ]           [] [] [] [ ? ]