[Bug rtl-optimization/48830] [4.6 regression] unrecognized insn: storing invalid upper FP reg in SImode
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48830 Jakub Jelinek changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED Target Milestone|4.6.4 |4.7.0 --- Comment #20 from Jakub Jelinek 2013-04-12 16:18:02 UTC --- The 4.6 branch has been closed, fixed in GCC 4.7.0.
[Bug rtl-optimization/48830] [4.6 regression] unrecognized insn: storing invalid upper FP reg in SImode
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48830 --- Comment #19 from Eric Botcazou 2012-07-19 15:28:24 UTC --- > I see something similar with gcc 4.5.3 when compiling mrtg: > > ./src/rateup.c:1136:1: error: insn does not satisfy its constraints: > (insn 11219 11218 3096 307 ./src/rateup.c:913 (set (mem/c:SI (reg:DI 2 %g2) > [23 > %sfp+-10660 S4 A32]) > (reg:SI 65 %f33 [+4 ])) 50 {*movsi_insn} (nil)) > ./src/rateup.c:1136:1: internal compiler error: in > reload_cse_simplify_operands, at postreload.c:396 > > (this has originally been reported as http://gnats.netbsd.org/46719) > > Is this the samme issue? Any chance of a fix for the 4.5 branch? This indeed looks like the same issue. But no fix is planned for 4.5.x (the branch is now closed) or 4.6.x (too risky). The workaround is usually trivial (lower the optimization level).
[Bug rtl-optimization/48830] [4.6 regression] unrecognized insn: storing invalid upper FP reg in SImode
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48830 Martin Husemann changed: What|Removed |Added CC||martin at netbsd dot org --- Comment #18 from Martin Husemann 2012-07-19 13:56:11 UTC --- I see something similar with gcc 4.5.3 when compiling mrtg: ./src/rateup.c:1136:1: error: insn does not satisfy its constraints: (insn 11219 11218 3096 307 ./src/rateup.c:913 (set (mem/c:SI (reg:DI 2 %g2) [23 %sfp+-10660 S4 A32]) (reg:SI 65 %f33 [+4 ])) 50 {*movsi_insn} (nil)) ./src/rateup.c:1136:1: internal compiler error: in reload_cse_simplify_operands, at postreload.c:396 (this has originally been reported as http://gnats.netbsd.org/46719) Is this the samme issue? Any chance of a fix for the 4.5 branch?