public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: gabor@mac.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: target/10282: [3.3/3.4 regression] ICE: unable to find a register to spill in class `Q_REGS' Date: Tue, 01 Apr 2003 00:07:00 -0000 [thread overview] Message-ID: <20030401000725.8760.qmail@sources.redhat.com> (raw) Old Synopsis: ICE: unable to find a register to spill in class `Q_REGS' New Synopsis: [3.3/3.4 regression] ICE: unable to find a register to spill in class `Q_REGS' State-Changed-From-To: open->analyzed State-Changed-By: bangerth State-Changed-When: Tue Apr 1 00:07:24 2003 State-Changed-Why: Confirmed. This is as short as I could get it: ------------------------ typedef struct X { char * p; long l; } X_t; void foo(X_t * A_buf , X_t * A_next) { int Li; long Ll; X_t Ld1; X_t Ld2; Li = undeclared1(Ll); Ld1 = *A_next; Ld2 = *A_buf; (*(Ld2.p + Ld1.l)) = Ll; undeclared2(Ld2); } ------------------------- g/x> /home/bangerth/bin/gcc-3.4-pre/bin/gcc -O -c x.c x.c: In function `foo': x.c:17: error: unable to find a register to spill in class `Q_REGS' x.c:17: error: this is the insn: (insn 22 20 24 0 0x40153268 (set (mem:QI (plus:SI (subreg:SI (reg/v:DI 63 [ Ld2 ]) 0) (subreg:SI (reg/v:DI 62 [ Ld1 ]) 4)) [0 S1 A8]) (subreg:QI (reg/v:SI 4 esi [orig:61 Ll ] [61]) 0)) 48 {*movqi_1} (insn_list 18 (insn_list 20 (nil))) (expr_list:REG_DEAD (reg/v:SI 4 esi [orig:61 Ll ] [61]) (expr_list:REG_DEAD (reg/v:DI 62 [ Ld1 ]) (nil)))) x.c:17: internal compiler error: in spill_failure, at reload1.c:1917 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. This is a regression on 3.3 and mainline w.r.t. 3.4. W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10282
next reply other threads:[~2003-04-01 0:07 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-01 0:07 bangerth [this message] 2003-04-01 16:56 Janis Johnson 2003-04-10 17:08 ebotcazou 2003-04-12 11:26 ebotcazou
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=20030401000725.8760.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=gabor@mac.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).