Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.development    |    Operating system development chatter    |    4,255 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,516 of 4,255    |
|    mutazilah@gmail.com to All    |
|    a.out    |
|    28 Nov 22 03:46:22    |
      From: muta...@gmail.com              Can the a.out format cope with medium and       compact memory models where code pointers       and data pointers are different sizes?              I'm thinking it doesn't matter for object code       where you could use a 32-bit address for both.              When used as an executable format, I'm thinking       it will also work. Normally you're only supposed       to update 2 bytes (the segment). E.g.              mov ax,DGROUP              can only cope with 2 bytes being fixed up.              But all references are like that - just segments.              So if the a.out executable has a 32-bit address       of the 2 bytes that need to be fixed, the loader       just needs to know that the offset, if it exists       at all, is already correct, so only update the       segment portion.              It's all very hazy still.              BFN. Paul.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca