public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: glen@imodulo.com To: gcc-gnats@gcc.gnu.org Subject: optimization/6822: GCC 3.1.1 - Internal compiler error in extract_insn, at recog.c:2132 Date: Sun, 26 May 2002 12:26:00 -0000 [thread overview] Message-ID: <20020526191538.6608.qmail@sources.redhat.com> (raw) >Number: 6822 >Category: optimization >Synopsis: GCC 3.1.1 - Internal compiler error in extract_insn, at recog.c:2132 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Sun May 26 12:16:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Glen Nakamura >Release: gcc version 3.1.1 20020526 (prerelease) >Organization: >Environment: i586-pc-linux-gnu >Description: Compiling testcase results in the following ICE: ice.c: In function `main': ice.c:12: unrecognizable insn: (insn:QI 59 24 60 (set (reg:CC 17 flags) (compare:CC (reg/v:QI 61) (const_int 128 [0x80]))) -1 (insn_list 24 (nil)) (expr_list:REG_DEAD (reg/v:QI 61) (nil))) ice.c:12: Internal compiler error in extract_insn, at recog.c:2132 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. The testcase compiles fine w/ the GCC 3.1 release. Possible regression on branch w.r.t. GCC 3.1... >How-To-Repeat: gcc -O2 ice.i >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="ice.i" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="ice.i" IyAxICJpY2UuYyIKIyAxICI8YnVpbHQtaW4+IgojIDEgIjxjb21tYW5kIGxpbmU+IgojIDEgImlj ZS5jIgp1bnNpZ25lZCBjaGFyCmZvbyAoKQp7CiAgICByZXR1cm4gMTI4Owp9CgppbnQKbWFpbiAo KQp7CiAgICB1bnNpZ25lZCBjaGFyIHEgPSBmb28gKCk7CiAgICByZXR1cm4gKHEgPCAweDgwKSA/ IDY0IDogMDsKfQo=
next reply other threads:[~2002-05-26 19:16 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-26 12:26 glen [this message] 2002-05-26 16:46 paolo 2002-05-28 7:10 Glen Nakamura 2002-05-28 8:16 Glen Nakamura 2002-05-28 11:00 Richard Henderson 2002-05-28 16:36 Eric Botcazou 2002-05-28 17:16 Eric Botcazou 2002-05-28 18:16 Glen Nakamura 2002-05-29 0:46 Glen Nakamura 2002-05-29 9:16 Eric Botcazou 2002-05-29 9:44 Glen Nakamura 2002-05-29 10:36 Richard Henderson 2002-05-29 12:16 Richard Henderson 2002-05-30 16:56 rth 2002-06-02 12:36 Richard Henderson 2002-06-02 13:06 Glen Nakamura
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=20020526191538.6608.qmail@sources.redhat.com \ --to=glen@imodulo.com \ --cc=gcc-gnats@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).