Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!rutgers!cbmvax!cbmehq!babylon!rbabel
From: rbabel@babylon.rmt.sub.org (Ralph Babel)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Help! (AmigaDOS CreateProc/LoadSeg)
Message-ID: <06569.AA06569@babylon.rmt.sub.org>
Date: 12 Mar 91 19:08:21 GMT
References: <63329@eerie.acsu.Buffalo.EDU> <19578@cbmvax.commodore.com> <06417.AA06417@babylon.rmt.sub.org> <ROSENBER.91Mar11193029@ra.abo.fi> <1991Mar12.123403.2415@odin.diku.dk>
Reply-To: cbmvax.commodore.com!cbmehq!babylon!rbabel (Ralph Babel)
Lines: 22

In article <1991Mar12.123403.2415@odin.diku.dk>,
bombadil@diku.dk (Kristian Nielsen) writes:

> /* Static initialised data (really code). */
> struct CodeHdr fooSegList={
>   sizeof(struct CodeHdr),
>   NULL,
>   0x4EF9,
>   (APTR)foo
> };

Same problem: not necessarily longword-aligned.

> (if LoadSeg differentiates between CODE and DATA sections,
> it might be nessesary to ensure that the structure is
> placed in the CODE section;

Currently it doesn't, but you never know.

Some compilers move "const" data into the code hunk.

Ralph