https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41565
--- Comment #14 from Richard Biener ---
It should happen everywhere, no explicit lto1 invocation should be necessary.
> ./xgcc -B. t.c -flto -c
> ./xgcc -B. t.o -m32
/usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin/ld:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41565
Eric Gallager changed:
What|Removed |Added
Status|NEW |ASSIGNED
Last reconfirmed|2009-10-04
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41565
Eric Gallager changed:
What|Removed |Added
Status|WAITING |NEW
CC|
--- Comment #8 from rguenth at gcc dot gnu dot org 2009-10-13 12:42 ---
Subject: Bug 41565
Author: rguenth
Date: Tue Oct 13 12:42:30 2009
New Revision: 152705
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=152705
Log:
2009-10-13 Richard Guenther rguent...@suse.de
PR
--- Comment #9 from rguenth at gcc dot gnu dot org 2009-10-13 12:43 ---
Still no testcase for the original report. Target options in general should
be fixed now.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #11 from pinskia at gcc dot gnu dot org 2009-10-13 22:40
---
Simple testcase for powerpc64.
int main(void){ return 0; }
--- CUT --
gcc t.c -flto -c -m64
/home/apinski/gcc-mainline/libexec/gcc/powerpc64-unknown-linux-gnu/4.5.0/lto1
t.o -m32
--- CUT ---
I have not
--- Comment #6 from pinskia at gcc dot gnu dot org 2009-10-08 23:06 ---
I ran into this again, this time on powerpc-linux-gnu when I forgot to include
-maltivec on the link line.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41565
--- Comment #7 from pinskia at gcc dot gnu dot org 2009-10-08 23:08 ---
Oh -maltivec is even weirder than -m32 as it does not change the ABI (well it
does but not with respect non vector arguments and such) but I should be able
to compile some files with -maltivec and some without.
--- Comment #5 from rguenth at gcc dot gnu dot org 2009-10-05 09:49 ---
There is one common problem with handling of target options - we do not
properly adjust the flag_var.
But - I cannot reproduce the original problem. Care to attach a testcase?
I always get linker complaints like
--- Comment #1 from rguenth at gcc dot gnu dot org 2009-10-04 09:25 ---
Awww - we have the concept of user options for this. See lto-opts.c.
We should somehow include this - but the multilibs do not fit the regular
options scheme really ... :/
--
rguenth at gcc dot gnu dot org
--- Comment #2 from rguenth at gcc dot gnu dot org 2009-10-04 09:54 ---
I'll see if I can fix it.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from rguenth at gcc dot gnu dot org 2009-10-04 09:58 ---
Btw, mixing any flags that change the set of builtin functions also is going
to confuse the streamer a lot.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41565
--- Comment #4 from joseph at codesourcery dot com 2009-10-04 12:17 ---
Subject: Re: New: -m32 causes an ICE when the object files
were compiled with 64bit
While this case should give a sensible error (not an ICE), linking an
object built with a 32-bit compiler with no special
13 matches
Mail list logo