Summary: | [4.3 regression] qt-4.3.4 compile failure with message "unable to find a register to spill in class 'R0_REGS'" | ||
---|---|---|---|
Product: | gcc | Reporter: | CHIKAMA Masaki <masaki.chikama> |
Component: | target | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | gcc-bugs, kkojima |
Priority: | P3 | Keywords: | ice-on-valid-code |
Version: | 4.3.0 | ||
Target Milestone: | --- | ||
Host: | Target: | sh4-*-linux | |
Build: | sh4-redhat-linux | Known to work: | |
Known to fail: | 4.3.1 4.4.0 | Last reconfirmed: | |
Attachments: |
preprocessed file generated by adding -save-temps
preprocessed file without precompiled headers |
Description
CHIKAMA Masaki
2008-07-01 10:09:49 UTC
Created attachment 15839 [details]
preprocessed file generated by adding -save-temps
Could you please send the testcase without using precompiled headers? See http://gcc.gnu.org/bugs.html#pch. I also suspect this is a duplicate of PR36684. Does -fno-schedule-insns get rid of this error? >Could you please send the testcase without using precompiled headers? Do you mean that I should redo without "-include .pch/release-shared/QtGui" ? I'll attach in next post. >Does -fno-schedule-insns get rid of this error? Yes. It passed without failure. Is this a workaround or right fix ? Created attachment 15842 [details]
preprocessed file without precompiled headers
gzipped beacuse plain text file's size is 1.5MB
Thanks for the updated testcase. I've confirmed that this PR is a duplicate of PR36684 as you suggested. > Is this a workaround or right fix ? SH backend enables first insn scheduling pass for SH4 when the estimated R0 register pressure is low. PR36684 reveals that it doesn't work well for PIC which will make many implicit R0 uses. It seems that there is no easy way to compute accurate R0 register pressure in that case. Also this optimization doesn't make much difference in performance for such case. So disabling it for PIC would be a reasonable fix, I guess. I'll prepare such patch for PR36684. *** This bug has been marked as a duplicate of 36684 *** Thank you. I'll learn more about background of this problem along with your comment. |