public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/37270] New: [4.4 Regression] SH: spill failure for R0_REGS Date: Thu, 28 Aug 2008 23:13:00 -0000 [thread overview] Message-ID: <bug-37270-5208@http.gcc.gnu.org/bugzilla/> (raw) The trunk compiler fails to compile libffi.call/cls_8byte.c with -O2 -fomit-frame-pointer. Here is a reduced test case: typedef struct s8 { int a; float b; } s8; s8 s8_fn (struct s8 a1, struct s8 a2) { struct s8 result; result.b = a1.b + a2.b; bar (a1.a, a1.b, a2.a, a2.b, result.a, result.b); return result; } With -O2 -fomit-frame-pointer, it causes foo.c:15: error: unable to find a register to spill in class 'R0_REGS' foo.c:15: error: this is the insn: (insn:HI 23 44 45 3 foo.c:14 (parallel [ (set (subreg:SF (reg:SI 1 r1 [orig:174 D.1226+4 ] [174]) 0) (reg:SF 163 [ D.1218 ])) (use (reg/v:PSI 151 )) (clobber (scratch:SI)) ]) 205 {movsf_ie} (expr_list:REG_DEAD (reg:SF 163 [ D.1218 ]) (nil))) foo.c:15: internal compiler error: in spill_failure, at reload1.c:2098 -- Summary: [4.4 Regression] SH: spill failure for R0_REGS Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: kkojima at gcc dot gnu dot org GCC target triplet: sh4-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37270
next reply other threads:[~2008-08-28 23:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-28 23:13 kkojima at gcc dot gnu dot org [this message] 2008-08-29 4:46 ` [Bug target/37270] " pinskia at gcc dot gnu dot org 2008-08-29 5:01 ` kkojima at gcc dot gnu dot org 2008-08-30 22:26 ` kkojima at gcc dot gnu dot org 2008-08-31 0:29 ` kkojima at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-37270-5208@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).