[Bug rtl-optimization/48128] Excessive code generated for vectorized loop

2021-08-26 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48128 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |4.8.0 Status|NEW

[Bug rtl-optimization/48128] Excessive code generated for vectorized loop

2014-06-18 Thread d.g.gorbachev at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48128 --- Comment #4 from Dmitry Gorbachev --- (In reply to comment #2) > When marking baz as static an compiling with -mno-sse, the result is even > more strange... Still true for GCC 4.9.1 and 4.10.0.

[Bug rtl-optimization/48128] Excessive code generated for vectorized loop

2011-03-15 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48128 Richard Guenther changed: What|Removed |Added Target|i686-*-*|i686-*-*, x86_64-*-* Statu

[Bug rtl-optimization/48128] Excessive code generated for vectorized loop

2011-03-14 Thread d.g.gorbachev at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48128 --- Comment #2 from Dmitry Gorbachev 2011-03-15 00:57:30 UTC --- When marking baz as static an compiling with -mno-sse, the result is even more strange...

[Bug rtl-optimization/48128] Excessive code generated for vectorized loop

2011-03-14 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48128 --- Comment #1 from Andrew Pinski 2011-03-15 00:16:10 UTC --- The problem is CSE, is CSEing the address of baz which confuses the register allocator because of not enough registers to work with on x86.