When on a solaris-usparc-gcc system "as" is GNU-as and not the system as
(which can happen if the directory containing all the GNU tools occurs
early in the PATH -- can we at least rely on the real "as" being
available on all systems?), you get lots of error messages:
gcc -E asm/sparcv8plus.S | as -xarch=v8plus /dev/fd/0 -o asm/sparcv8plus-gcc.o
bn_asm.sparc.v8plus.S: Assembler messages:
bn_asm.sparc.v8plus.S:162: Error: Illegal operands
bn_asm.sparc.v8plus.S:174: Error: Unknown opcode: `stuw'
bn_asm.sparc.v8plus.S:183: Error: Unknown opcode: `stuw'
bn_asm.sparc.v8plus.S:192: Error: Unknown opcode: `stuw'
bn_asm.sparc.v8plus.S:201: Error: Unknown opcode: `stuw'
[...]
(I observed this with GNU as version 2.8.1.)
Is there a way to write that file in a way that works also with GNU
as, or is there a not-too-inconvenient way to make sure that the
system "as" is used no matter what PATH says?
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
