Amiga Hunk - Revision history

Jsummers: Category:Amiga

2018-05-14T19:34:01Z

Category:Amiga

Kyz: /* Loadable format */

2018-05-12T11:16:47Z

‎Loadable format

Kyz: /* Structure */

2018-05-12T11:14:39Z

‎Structure

Kyz at 13:16, 10 May 2018

2018-05-10T13:16:37Z

Kyz: /* Structure */

2018-05-10T13:09:37Z

‎Structure

Kyz: /* Structure */

2018-05-10T13:00:32Z

‎Structure

Kyz: /* Structure */

2018-05-10T12:50:08Z

‎Structure

Kyz at 12:49, 10 May 2018

2018-05-10T12:49:15Z

Kyz: /* Identification */

2018-05-10T12:28:25Z

‎Identification

Kyz at 12:28, 10 May 2018

2018-05-10T12:28:00Z

← Older revision		Revision as of 19:34, 14 May 2018
Line 33:		Line 33:
	* Ralph Babel. "The Format of Load and Object Modules" ''The Amiga Guru Book'', self-published, 1993, p657-682		* Ralph Babel. "The Format of Load and Object Modules" ''The Amiga Guru Book'', self-published, 1993, p657-682
	* http://amiga-dev.wikidot.com/file-format:hunk		* http://amiga-dev.wikidot.com/file-format:hunk
		+
		+	[[Category:Amiga]]

@@ Line 24: / Line 24: @@
 * One or more HUNK_CODE, HUNK_DATA or HUNK_BSS hunks, each of which comprises:
 ** The code/data for a code/data hunk
-** Zero or more blocks for this hunk: all can have HUNK_SYMBOL, HUNK_DEBUG. Code/data can also have HUNK_RELOC32, HUNK_RELOC32SHORT, HUNK_DREL32, HUNK_ABSRELOC16 relocations
+** Zero or more blocks for this hunk: all can have HUNK_SYMBOL or HUNK_DEBUG blocks. Code/data can also have HUNK_RELOC32, HUNK_RELOC32SHORT, HUNK_DREL32 or HUNK_ABSRELOC16 relocation blocks
 ** Hunks always end with a HUNK_END block

@@ Line 12: / Line 12: @@
 == Structure ==
-The loadable format begins with a fixed header, followed by a series of ''hunks''. each one of which is considered an independent ''segment'' by AmigaDOS. These hunks can either be code, data, or zeroed memory (BSS).
+=== Loadable format ===
+Hunks themselves can contain optional ''blocks'', for code relocations and debug symbols.
-Hunks themselves can contain optional ''blocks'', including code relocations and debug symbols.
 All Amiga programs share the same address space and are loaded to wherever there is free memory. They cannot be loaded to specific absolute addresses. This means code must either be written in a position-independent fashion, or it can use ''relocation'' blocks to specify where the loader has to fix up absolute address references.
 Amiga programs do their own dynamic linking with OS functions such as <tt>OpenLibrary</tt>, which loads and returns a pointer to a shared library, whose functions can then be executed by jumping to specific offsets from the pointer. This is unlike Windows and UNIX where the loader is expected to fetch and link in other libraries while loading the program.
 == Format specification ==

@@ Line 12: / Line 12: @@
 == Structure ==
-The loadable format begins with a fixed header, followed by a series of ''hunks''. each one of which is considered an independent ''segment'' by AmigaDOS. These hunks can either be code, data, or uninitialised memory (BSS).
+The loadable format begins with a fixed header, followed by a series of ''hunks''. each one of which is considered an independent ''segment'' by AmigaDOS. These hunks can either be code, data, or zeroed memory (BSS).
 Hunks themselves can contain optional ''blocks'', including code relocations and debug symbols.
-All Amiga programs share the same address space and are loaded to wherever there is free memory. They cannot be loaded to specific absolute addresses. This means code must either be written in a position-independent fashion, or it can use ''relocation'' blocks to specify where the loader has to fix up absolute address references to other parts of the code.
+All Amiga programs share the same address space and are loaded to wherever there is free memory. They cannot be loaded to specific absolute addresses. This means code must either be written in a position-independent fashion, or it can use ''relocation'' blocks to specify where the loader has to fix up absolute address references.
 Amiga programs do their own dynamic linking with OS functions such as <tt>OpenLibrary</tt>, which loads and returns a pointer to a shared library, whose functions can then be executed by jumping to specific offsets from the pointer. This is unlike Windows and UNIX where the loader is expected to fetch and link in other libraries while loading the program.

@@ Line 12: / Line 12: @@
 == Structure ==
-The format begins with a fixed header, followed by a series of ''hunks'' which can contain different types of data, such as code, data, uninitialised memory reservations (BSS), code relocations, debug symbols and so on.
+The loadable format begins with a fixed header, followed by a series of ''hunks''. each one of which is considered an independent ''segment'' by AmigaDOS. These hunks can either be code, data, or uninitialised memory (BSS).
-All Amiga programs share the same address space and are loaded to wherever there is free memory. They cannot be loaded to specific absolute addresses. This means code must either be written in a position-independent fashion, or it can use ''relocation'' hunks to specify where the loader has to fix up absolute address references to other parts of the code.
+Hunks themselves can contain optional ''blocks'', including code relocations and debug symbols.
 Amiga programs do their own dynamic linking with OS functions such as <tt>OpenLibrary</tt>, which loads and returns a pointer to a shared library, whose functions can then be executed by jumping to specific offsets from the pointer. This is unlike Windows and UNIX where the loader is expected to fetch and link in other libraries while loading the program.

@@ Line 16: / Line 16: @@
 All Amiga programs share the same address space and are loaded to wherever there is free memory. They cannot be loaded to specific absolute addresses. This means code must either be written in a position-independent fashion, or it can use ''relocation'' hunks to specify where the loader has to fix up absolute address references to other parts of the code. Once loaded, they cannot be relocated again, only unloaded and reloaded.
-Amiga programs do their own dynamic linking with OS functions such as <tt>OpenLibrary</tt>, which loads and returns a pointer to a shared library, whose functions can then be executed by jumping to specific offsets from the pointer. This is unlike Windows and UNIX where the loader is expected to fetch and link in other libraries at loading the program, and programs have "import" and "export" symbols. Amiga programs do not have to list any symbols or name any other libraries, even if they depend on them to run. Amiga programs can include a list of their own "symbols" for use by debuggers, but aren't required to do so.
+Amiga programs do their own dynamic linking with OS functions such as <tt>OpenLibrary</tt>, which loads and returns a pointer to a shared library, whose functions can then be executed by jumping to specific offsets from the pointer. This is unlike Windows and UNIX where the loader is expected to fetch and link in other libraries while loading the program, and programs have "import" and "export" symbols. Amiga programs do not have to list any symbols or name any other libraries, even if they depend on them to run. Amiga programs can include a list of their own "symbols" for use by debuggers, but aren't required to do so.
 == Format specification ==

← Older revision		Revision as of 12:49, 10 May 2018
Line 10:		Line 10:

	Object code and link libraries begin with the magic ID {{magic\|00 00 03 E7}}. These files have to be combined into a loadable file using a linker to get an executable program.		Object code and link libraries begin with the magic ID {{magic\|00 00 03 E7}}. These files have to be combined into a loadable file using a linker to get an executable program.
		+
		+	== Structure ==
		+	The format begins with a fixed header, followed by a series of ''hunks'' which can contain different types of data, such as code, data, uninitialised memory reservations (BSS), code relocations, debug symbols and so on.
		+
		+	All Amiga programs share the same address space and are loaded to wherever there is free memory. They cannot be loaded to specific absolute addresses. This means code must either be written in a position-independent fashion, or it can use ''relocation'' hunks to specify where the loader has to fix up absolute address references to other parts of the code. Once loaded, they cannot be relocated again, only unloaded and reloaded.
		+
		+	Amiga programs do their own dynamic linking with OS functions such as <tt>OpenLibrary</tt>, which loads and returns a pointer to a shared library, whose functions can then be executed by jumping to specific offsets from the pointer. This is unlike Windows and UNIX where the loader is expected to fetch and link in other libraries at loading the program, and programs have "import" and "export" symbols. Amiga programs do not have to list any symbols or name any other libraries, even if they depend on them to run. Amiga programs can include a list of their own "symbols" for use by debuggers, but aren't required to do so.

	== Format specification ==		== Format specification ==

@@ Line 7: / Line 7: @@
 == Identification ==
-Loadable files begin with the magic ID {{magic|00 00 03 F3}}. "Loadable" includes all directly executable files, as well as shared libraries, device drivers, filesystem handlers, datatypes and most other "plugins".
+Loadable files begin with the magic ID {{magic|00 00 03 F3}}. "Loadable" includes all directly executable files, as well as shared libraries, device drivers, filesystem handlers, datatypes and other "plugins".
 Object code and link libraries begin with the magic ID {{magic|00 00 03 E7}}. These files have to be combined into a loadable file using a linker to get an executable program.

@@ Line 4: / Line 4: @@
 }}
-The ''Amiga Hunk'' format is the native file format of AmigaOS for loadable files (including all executable files), object code and link libraries.
+The '''Amiga Hunk''' format is the native file format of AmigaOS for loadable files (including all executable files), object code and link libraries.
 == Identification ==