llvm dev - Mar 2007 - [LLVMdev] gcc 4.1* carashes compiling llvm-gcc

Ferad Zyulkyarov wrote:
> By the way. I will use the opportunity to ask you again :) I tried to
> compile with gcc 4.0.4. It successfully compile LLVM but fails
> compiling LLVM's gcc front end. The problem is architectural 32 and 64
> bit. The machine has intel xeon CPU that is physically 32 bit but has
> 64 extension x86_64 (or something like that, I am not exactly sure).
> The error message that I get is bellow. I noticed also that the
> compilation command specifies "-m32" flag which probably
shouldn't be
> passed.
i had the same errors. adding "--disable-multilib" to configure solved
the problem. but i guess this is not a general solution.

florian

> i had the same errors. adding "--disable-multilib" to configure
solved
> the problem. but i guess this is not a general solution.
Thanks, that worked. Probably it would be good if this issue is
included in the readme file for gcc-front end.

Regards,
Ferad

-- 
Ferad Zyulkyarov
Barcelona Supercomputing Center

On Thu, 2007-03-29 at 15:57 +0200, Ferad Zyulkyarov
wrote:
> > i had the same errors. adding "--disable-multilib" to
configure solved
> > the problem. but i guess this is not a general solution.
> 
> Thanks, that worked. Probably it would be good if this issue is
> included in the readme file for gcc-front end.
The problem looked (to me) like an inline assembly issue. These messages
in particular:
> /tmp/ccCUQ9uX.s:11: Error: `completed.4804(%rip)' is not a valid
> base/index expression
> /tmp/ccCUQ9uX.s:17: Error: `p.4803(%rip)' is not a valid base/index
> expression
> /tmp/ccCUQ9uX.s:18: Error: bad register name `%rax'
> /tmp/ccCUQ9uX.s:20: Error: `p.4803(%rip)' is not a valid base/index
> expression
> /tmp/ccCUQ9uX.s:21: Error: bad register name `%rax)'
> /tmp/ccCUQ9uX.s:22: Error: bad register name `%rax'
> /tmp/ccCUQ9uX.s:25: Error: `completed.4804(%rip)' is not a valid
> base/index expression
All of the quoted code looks like inline assembly. It is likely these
are coming from system header files. If not, they may be coming from the
GCC runtime code. In order to debug this, you'd need to provide the
pre-processed input that was trying to be compiled. It is also possible
that the "host" machine for your machine was calculated incorrectly
and
you're attempting to compile assembly that doesn't match the machine.

Reid.