public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/33009] -frtl-abstract-sequences causes an infinite loop Date: Tue, 07 Aug 2007 14:37:00 -0000 [thread overview] Message-ID: <20070807143732.2317.qmail@sourceware.org> (raw) In-Reply-To: <bug-33009-11811@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from pinskia at gcc dot gnu dot org 2007-08-07 14:37 ------- I get an ICE: t.c: In function 'foo': t.c:28: error: unrecognizable insn: (insn 177 0 0 (set (reg:SI 0 ax) (symbol_ref:SI ("*L9") [flags 0x2])) -1 (nil)) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33009
next prev parent reply other threads:[~2007-08-07 14:37 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-08-07 13:49 [Bug c/33009] New: [dataflow] cc1 goes into " aldot at gcc dot gnu dot org 2007-08-07 14:32 ` [Bug rtl-optimization/33009] -frtl-abstract-sequences causes an " pinskia at gcc dot gnu dot org 2007-08-07 14:37 ` pinskia at gcc dot gnu dot org [this message] 2008-02-21 15:49 ` loki at gcc dot gnu dot org 2008-02-21 16:45 ` aldot at gcc dot gnu dot org 2008-02-29 13:08 ` loki at gcc dot gnu dot org 2008-03-05 10:17 ` loki at gcc dot gnu dot org 2008-03-05 10:28 ` loki at gcc dot gnu dot org 2008-03-05 14:27 ` dominiq at lps dot ens dot fr 2008-03-05 14:37 ` loki at gcc dot gnu dot org 2008-03-05 15:41 ` dominiq at lps dot ens dot fr 2008-03-05 20:54 ` dominiq at lps dot ens dot fr 2008-03-05 22:27 ` dominiq at lps dot ens dot fr 2008-03-06 7:33 ` dominiq at lps dot ens dot fr 2008-03-06 17:59 ` [Bug rtl-optimization/33009] [4.4 Regression] -frtl-abstract-sequences causes an ICE belyshev at depni dot sinp dot msu dot ru 2008-03-07 12:33 ` loki at gcc dot gnu dot org 2008-03-07 12:48 ` [Bug rtl-optimization/33009] -frtl-abstract-sequences causes an infinite loop belyshev at depni dot sinp dot msu dot ru 2008-03-24 14:46 ` eric dot weddington at atmel dot com
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=20070807143732.2317.qmail@sourceware.org \ --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).