Mail Archives: djgpp/1997/11/06/18:56:09
At 07:48 11/5/1997 EST, VANGEL AT vmredipn DOT ipn DOT mx wrote:
>Subject:About Reserved Words about AT&T
>
>Hi all.
>
>I'm learning all about ASM of AT&T with DJGPP V.2 ... and I have any
>problems about the reserved words at ASM with AT&T ...
>
>For instance:
>
>ASM INTEL ASM AT&T
>--------- --------
>mov al,0FFH movl $OxFF, %al
>mov ax,1 movw $1, %ax
>mov ah, byte prt X movw X, %ah
>.................................
The first and third AT&T opcodes should be `movb'. But anyway...
>The last lines are easy for learn ... :) ... but there are any
>reserved words at Intel what I can't equivalent in DJGPP ...
By "reserved words" I assume you mean opcodes. The answer is no. Every
documented assembly opcode understood by the 386 has an AT&T version, AFAIK.
>
>Where can I found all reserved words about ASM at AT&T ...?
>and ... which reserved words are available at DJGPP V.2 ...?
You'll need some kind of assembly language text to find what instructions
exist, and then you can translate them into AT&T. The existing opcodes are
CPU-dependent, and DJGPP's `as' assembler should support all of them. (With
the possible exception of MMX, but that's only for new Pentiums.)
>
>By the way, the arguments at __dpmi_regs have the option:
>
>--> __dpmi_regs.x.res ..... this argument is the equivalentat the
>
>register -->"esp" of the uP 386 of Intel ...?
Yes, technically, but it's called `res' because you aren't allowed to use
it, and it's REServed.
>
>Does anyone know how use this arguments ...? I've one PS/1 model
>2121-H82 with processor 386 ...and I think program in Protected
>Mode. Does anyone know about any guide for use all registers of this
>machine ...?
Again, any good 386 assembly language book.
Nate Eldredge
eldredge AT ap DOT net
- Raw text -