"Kendall Bennett" <[EMAIL PROTECTED]> writes:
> 1. The current assyntax.h mechanism is simply not portable. This
> mechanism relies on the availability of a *working* C pre-processor,
> and this is unfortunately not a luxury available on the DOS, Windows
> and OS/2 platforms.
I don't think that _anything_ is portable, given those standards. I
do think assyntax.h is more portable than NASM though. It can target
4 different assemblers (AT&T, GNU, ACK and NASM) where NASM syntax
only works with one assembler.
> Many compilers we use (Watcom C++ and Borland C++ specifically) do
> not handle C pre-processing very well, and did not work with the
> assyntax.h stuff. Visual C++ worked the best, and that is what we
> used to do the conversion.
Which is worse, requiring GNU users to install NASM when they already
have a working assembler, or requiring Watcom/Borland users to install
a working cpp to replace one that doesn't work correctly?
> 2. The current mechanism to get NASM'able assembler code simply did
> not work. We tried to use it, and modified the macros as much as we
> could to make it work, but the resulting assembler code would not
> build. Instead we had to hand modify the code from the Visual C++ pre-
> processed variants, which is what we will be checking in.
I thought the assembly code was working with VC++/NASM. Could you
tell me what went wrong?
(Make sure you disabled #line directives and use NASM 0.98 or newer.)
Josh
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
