TIP: Click on subject to list as thread! ANSI
echo: 80xxx
to: PAUL WANKADIA
from: BRIAN MCCLOUD
date: 1997-05-30 10:41:00
subject: DJGPP, gcc et al

PW>Having discovered the joys of '--oformat binary', I can now get myself a
PW>binary image when I compile.  Unfortunately, I now get a strange byte 
thrown
PW>into my code, namely 0x66.  According to one of the files with Ralfie's
list,
PW>it's some kind of prefix for 386+ to specify memory-size or something.  
Does
PW>anyone know how to get rid of it?  It doesn't seem to appear in code that
gcc
PW>generates...  TIA.
That prefix is the operand-size prefix, which is required for most
instructions that use 32-bit register/memory operands (in a Use16 segment...
a Use32 segment would need the byte to do 16-bit reg/mem operands)... however
I don't know how to get rid of it, since I don't know why your compiler is
adding it...  I think GCC is probably making a Use32 segment, so that the
instructions for 32-bit operands don't need the prefix.
((Cloud))
MauveCloud@juno.com
 * OLX 2.2 * Remember, even if you win the rat race -- you're still a
--- PCBoard (R) v15.3/M 10
---------------
* Origin: Next time, Dial The Wrong Number! (209) 943-1880 (1:208/205)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.