intel Syntax -> AT&T Syntax

intel Syntax -> AT&T Syntax

Post by i.. » Sat, 17 Oct 1998 04:00:00



hi
i got some problems with porting assemler code from windows nt to
linux (both x86 !!!). because of the different notation
windows : normal intel syntax
linux       : AT&T syntax
it is possible of course to rewrite the code in the new syntax but it
would be great if there is a tool witch can convert an Intel assembler
code to AT&T syntax assembler.
if anyone got some expirience with these syntax convertion or got some
cool ideas of solving these problem.
please E-Mail me  :


thx

 
 
 

intel Syntax -> AT&T Syntax

Post by William McBri » Sat, 17 Oct 1998 04:00:00


: it is possible of course to rewrite the code in the new syntax but it
: would be great if there is a tool witch can convert an Intel assembler
: code to AT&T syntax assembler.

There is apparently some automatic conversion for inline asm in the more
recent versions of FPC:

 http://www.brain.uni-freiburg.de/~klaus/fpc/

Perhaps this may be of help.

--
William McBrine    | http://www.clark.net/~wmcbrine/


 
 
 

1. inline assembler error - porting Intel syntax to AT&T syntax

// Intel syntax
void x( int *p ) {
  int example;
  __asm {
    mov esi, p
    mov  [ esi ], ebx
    mov [example], eax
   }

I'm porting the code to GCC, but got error

I couldn't access the data which *p points to, and got error like this:
    - error, undefined reference to `p'
I couldn't access varible example, and got error like this:
    - error, undefined  reference to `example'

and no error if it is a global varible

Can someone help me?

2. security

3. INTEL -> AT&T syntax-conversion ??

4. fips

5. AT&T asm syntax but not IBM asm syntax?

6. Find easy what you need for Linux

7. access.conf syntax error without a syntax error

8. System V Cron can't set login UID

9. apsfilter && syntax highlighting

10. Linux i386 assembler with Intel/Microsoft syntax?

11. gnu as and intel syntax.

12. <keygen name=...> tag syntax

13. 2.5.60 defconfig+CONFIG_MODVERSIONS=y -> syntax error