From: Charles D. <cha...@ho...> - 2005-03-31 23:29:40
|
>From: Daniel Foesch <kr...@gm...> >As far as 64-bit support, I'd really like to see us using GAS, but I >realize that would lock us a little further into GCC-isms. But GAS >and AT&T syntax just "feel" right to me after all these years of >working with it. Plus, GAS is already 64-bit capable. I know there was a discussion about this in November. IIRC, GAS can use Intel syntax using .intel_syntax anyway right? Besides that, though, wouldn't YASM be a better alternative to ease cross platform compatibility? Its features seem to really reflect what we need out of a 64-bit assembler (and more). <obligatory quote:> -Nearly feature-complete lexing and parsing of (preprocessed) NASM syntax. -AMD64 support (enabled using "BITS 64" and "-m amd64" option) -64-bit (and larger) integer constants allowed (including math operations). -Internationalization support via GNU gettext. -A simple 2-pass optimizer (it's a bit better than the NASM one). -The "real" NASM preprocessor (imported from NASM's source tree). -Binary object file output (NASM style). -C-OFF object file output, for use with DJGPP. -Win32 object file output (including Win64/AMD64 support). -STABS debug format. -ELF32 and ELF64 object file output. No debugging information included at this point. -Portability; currently compilable on: x UNIX and compatibles (FreeBSD and Linux tested, GNU configure based autoconfiguration) x DOS (using DJGPP) x Windows (using Visual C++ or CygWin). _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ |