[LLVMdev] Potential breakage in llvm-gcc's ./configure

[Joachim Durchholz]

Am Montag, den 24.03.2008, 11:37 -0400 schrieb Daniel Berlin:
> >
> >  Third, even with --target and --host explicitly set to
> >  i686-pc-linux-gnu, the assembler will be fed with 64-bit code. The
> >  failing command is
> >
> >  /home/jo/llvm-gcc-wrk/gcc/xgcc -B/home/jo/llvm-gcc-wrk/gcc/
> >  -B/home/jo/i686-pc-linux-gnu/bin/ -B/home/jo/i686-pc-linux-gnu/lib/
> >  -isystem /home/jo/i686-pc-linux-gnu/include
> >  -isystem /home/jo/i686-pc-linux-gnu/sys-include -O2 -DIN_GCC -W -Wall
> >  -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
> >  -Wold-style-definition -isystem ./include -I. -I.
> >  -I/home/jo/llvm-gcc-src/gcc -I/home/jo/llvm-gcc-src/gcc/.
> >  -I/home/jo/llvm-gcc-src/gcc/../include
> >  -I/home/jo/llvm-gcc-src/gcc/../libcpp/include -g0
> >  -finhibit-size-directive -fno-inline-functions -fno-exceptions
> >  -fno-zero-initialized-in-bss -fno-unit-at-a-time -fno-omit-frame-pointer
> >  -c /home/jo/llvm-gcc-src/gcc/crtstuff.c -DCRT_BEGIN -DCRTSTUFFT_O
> >  -o crtbeginT.o
> >
> >  (slightly edited to leave out multiple blanks and line continuation
> >  backslashes).
> >
> >  The error messages are just what I had seen earlier:
> >
> >  /tmp/ccVjR8Qt.s: Assembler messages:
> >  /tmp/ccVjR8Qt.s:33: Error: suffix or operands invalid for `push'
> >  /tmp/ccVjR8Qt.s:43: Error: suffix or operands invalid for `call'
> >  /tmp/ccVjR8Qt.s:61: Error: suffix or operands invalid for `push'
> >  /tmp/ccVjR8Qt.s:71: Error: suffix or operands invalid for `call'
> >
> 
> This is interesting, and I wonder if it appears in gcc itself. If so,
> it is a bug.

The problem persists even when submitting gcc-4.2 and g++-4.2 via
environment variables per your suggestion.
(The failing xgcc command has slightly different options, and the
reported line numbers differ slightly, but that's all.)

I don't know how to check whether it appears in gcc itself. I don't have
an xgcc command installed other than via llvm.

Regards,
Jo