Re: delete "0D"

Am Sat, 23 Aug 2008 02:33:29 -0700 (PDT) schrieb Alexei A. Frounze:

On Aug 23, 12:54 am, Dirk Wolfgang Glomp <d...@xxxxxxxxxxxxxxxxxxx>
wrote:
Am Fri, 22 Aug 2008 20:15:33 -0400 schrieb Frank Kotler:

J.Dorval wrote:
"Dirk Wolfgang Glomp" <d...@xxxxxxxxxxxxxxxxxxx> a écrit dans le message de
news: 1j16eimzxzhq$.11tsnlqksomiu$.__BEGIN_MASK_n#9g02mG7!__...__END_MASK_i?a63jfAD$z__@xxxxxxxxxxxxx
DATEN SEGMENT use32 'DATA'

Did you intend for this to be "use32", Dirk???

I think this results a data segment with a dword alignment.

That's possible, but I wouldn't rely on it. Use16/32 is primarily to
tell the assembler the addressing mode for which the code should be
generated (affects: 66 & 67 prefix generation and default operand and
address size and sometimes the immediate operand size, ModR/M+SIB
generation).

I think this is only for code segments importend, how can a datasegment
declaration perform a prefering acces of one of the both adressing modi?

For segment alignment there's ALIGN=.

MASM need a datasegment-declaration anyyway.

Dirk
.

Relevant Pages

  • Re: doubt in protected mode
    ... SpooK has given you a pretty good answer to this, but I'll try a slightly different "approach"... ... there's a linker involved, it's more than "assemble" that's happening. ... Is the map file coming from the assembler or the linker? ... something so ugly?), "code segment" and "data segment" is somewhat of an "abstraction", known only to the assembler/linker - at the "machine level" it's all just bytes. ...
    (alt.lang.asm)
  • Phew!
    ... I've a fair amount of programming experience, so I already had some basic concepts under my belt. ... I'm in the process of converting a little calendar program I wrote for CLISP over to assembler using nasm - the main problem being that one has nothing to work with. ... I then write a wrapper test function which plugs in some values, calls the routines, and fills out the results to a data segment. ...
    (comp.lang.asm.x86)