Article View: comp.sys.amiga.tech
Article #12540Re: Re^2: Atom / putting hunks in CHIP/FAST memory. and, 1.4 request
From: Andy Heffernan
Date: Sat, 06 May 1989 04:07
Date: Sat, 06 May 1989 04:07
39 lines
2344 bytes
2344 bytes
In article <247@medusa.informatik.uni-erlangen.de> mlelstv@immd4.informatik.uni-erlangen.de (Michael van Elst ) writes:
[...]
>The only thing that I want to point on is, that memory type information
>isn't placed in the hunk type fields BUT in the hunk size field.
That's not what I see.
A simple source file like:
----------------------------------------------------------------------
| int lonelyint; |
----------------------------------------------------------------------
When compiled with Lattice 5.02 using the -ab option (forcing bss data
to be allocated from chip RAM) produces an object file that looks like:
----------------------------------------------------------------------
| 0000: 000003E7 00000002 74657374 2E630000 ...g....test.c.. |
| 0010: 000003E9 00000000 000003F2 400003EB ...i.......r@..k |
| 0020: 00000001 000003EF 01000003 5F6C6F6E .......o...._lon |
| 0030: 656C7969 6E740000 00000000 00000000 elyint.......... |
| 0040: 000003F2 ...r |
----------------------------------------------------------------------
Note the two long words at offset 0x1c.
400003EB hunk_bss_chip (hunk_bss with bit 30 set)
00000001 allocate 1 long word at load time
Similar games can be played with code and initialized data hunks.
> Michael van Elst
>
>E-mail: UUCP: ...uunet!unido!fauern!faui45!mlelstv
--
-------------------------------------------------------------------------
Andy Heffernan uunet!glyph!nichiren [1222 - 1282]
-------------------------------------------------------------------------
Technical Details
Message-ID:
<194@glyph.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!glyph!nichirenReferences:
<8905012052.AA25549@postgres.Berkeley.EDU> <239@medusa.informatik.uni-erlangen.de> <190@glyph.UUCP> <247@medusa.informatik.uni-erlangen.de>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!glyph!nichiren From: nichiren@glyph.UUCP (Andy Heffernan) Newsgroups: comp.sys.amiga.tech Subject: Re: Re^2: Atom / putting hunks in CHIP/FAST memory. and, 1.4 request Message-ID: <194@glyph.UUCP> Date: 6 May 89 04:07:48 GMT References: <8905012052.AA25549@postgres.Berkeley.EDU> <239@medusa.informatik.uni-erlangen.de> <190@glyph.UUCP> <247@medusa.informatik.uni-erlangen.de> Reply-To: nichiren@glyph.UUCP (Andy Heffernan) Organization: Glyph UNIX, Kingston, NY Lines: 39