[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2021-09-15 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 Richard Biener changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2021-09-15 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 --- Comment #15 from Andrew Pinski --- I suspect this has been fixed since maybe GCC 8 (maybe GCC 7).

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-09-12 Thread thiago at kde dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 --- Comment #14 from Thiago Macieira 2012-09-12 13:02:23 UTC --- >From GCC's own manual: (Node "Function attributes"): On the 386/x86_64 and PowerPC backends, the inliner will not inline a function that has different target options th

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-08-13 Thread thiago at kde dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 --- Comment #13 from Thiago Macieira 2012-08-13 12:13:40 UTC --- (In reply to comment #12) > Yes, there are similar option-related bugs for this. Note somebody needs > to sit down and document the desired semantics of combining translation > uni

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-08-13 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 --- Comment #12 from Richard Guenther 2012-08-13 11:58:33 UTC --- (In reply to comment #9) > (In reply to comment #8) > > If you do something like > > > > gcc -c t1.c -mavx -flto > > gcc -c t2.c -msse2 -flto > > gcc t1.o t2.o -flto > > > > t

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-08-13 Thread thiago at kde dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 --- Comment #11 from Thiago Macieira 2012-08-13 10:12:48 UTC --- Attaching __attribute__((target("xxx"))) to the function does help. It generates the following with the my_bzero function from comment 2: 02e0 : 2e0: test %rsi,%r

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-08-13 Thread thiago at kde dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 --- Comment #10 from Thiago Macieira 2012-08-13 09:53:32 UTC --- Another test: $ cat main_avx.c #define BZERO bzero_avx #pragma GCC target ("avx") #include "main.c" $ cat main_sse2.c #define BZERO bzero_sse2 #pragma GCC target ("sse2") #include

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-08-13 Thread thiago at kde dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 --- Comment #9 from Thiago Macieira 2012-08-13 09:44:51 UTC --- (In reply to comment #8) > If you do something like > > gcc -c t1.c -mavx -flto > gcc -c t2.c -msse2 -flto > gcc t1.o t2.o -flto > > then the link step will use -mavx -msse2, th

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-08-13 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 --- Comment #8 from Richard Guenther 2012-08-13 08:59:18 UTC --- If you do something like gcc -c t1.c -mavx -flto gcc -c t2.c -msse2 -flto gcc t1.o t2.o -flto then the link step will use -mavx -msse2, that is, target options are concatenated

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-08-11 Thread steven at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 Steven Bosscher changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-08-11 Thread thiago at kde dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 --- Comment #6 from Thiago Macieira 2012-08-11 23:23:39 UTC --- (In reply to comment #5) > "Fixing" this in the compiler isn't straight-forward. The _mm_stream functions > are just wrappers around builtin functions. It may work correctly if you p

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-08-11 Thread steven at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 --- Comment #5 from Steven Bosscher 2012-08-11 22:46:31 UTC --- "Fixing" this in the compiler isn't straight-forward. The _mm_stream functions are just wrappers around builtin functions. It may work correctly if you put the bzero functions in two

[Bug lto/54231] LTO generates code for the wrong CPU if different options used

2012-08-11 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54231 Andrew Pinski changed: What|Removed |Added Component|c |lto Severity|normal