public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/52306] ICE in CSE Date: Thu, 06 Dec 2012 09:53:00 -0000 [thread overview] Message-ID: <bug-52306-4-KoxY6kdcN7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52306-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52306 --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-12-06 09:52:46 UTC --- cselib.c ICEs if it sees an invalid insn, i.e. one that modifies the same register or memory more than once. So it is a bug in whatever pass created that insn.
next prev parent reply other threads:[~2012-12-06 9:53 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-18 23:32 [Bug middle-end/52306] New: " tg at mirbsd dot org 2012-03-25 12:47 ` [Bug middle-end/52306] " aoliva at gcc dot gnu.org 2012-03-25 13:51 ` aoliva at gcc dot gnu.org 2012-05-06 14:29 ` tg at mirbsd dot org 2012-05-06 17:05 ` tg at mirbsd dot org 2012-12-04 9:27 ` tg at mirbsd dot org 2012-12-04 10:29 ` mikpe at it dot uu.se 2012-12-04 12:59 ` tg at mirbsd dot org 2012-12-04 22:06 ` mikpe at it dot uu.se 2012-12-06 9:50 ` mikpe at it dot uu.se 2012-12-06 9:53 ` jakub at gcc dot gnu.org [this message] 2012-12-24 0:53 ` tg at mirbsd dot org 2013-01-29 21:17 ` [Bug middle-end/52306] ICE in cselib_record_set, at cselib.c:2158 tg at mirbsd dot org 2013-01-29 21:26 ` tg at mirbsd dot org 2013-01-29 23:30 ` tg at mirbsd dot org 2013-01-30 17:34 ` mikpe at it dot uu.se 2013-01-30 17:50 ` mikpe at it dot uu.se 2013-02-06 23:25 ` mikpe at it dot uu.se 2013-02-07 8:14 ` jakub at gcc dot gnu.org 2013-08-17 17:31 ` tg at mirbsd dot org 2013-08-17 18:44 ` tg at mirbsd dot org 2013-08-22 16:28 ` tg at mirbsd dot org 2013-12-19 9:02 ` schwab@linux-m68k.org 2013-12-19 10:40 ` mikpelinux at gmail dot com 2013-12-19 11:12 ` [Bug middle-end/52306] [4.8/4.9 regression] " ebotcazou at gcc dot gnu.org 2013-12-19 11:22 ` schwab@linux-m68k.org 2013-12-19 11:28 ` amker.cheng at gmail dot com 2013-12-19 15:18 ` rguenth at gcc dot gnu.org 2014-02-10 5:37 ` law at redhat dot com 2014-02-10 16:26 ` [Bug middle-end/52306] [4.8 " law at redhat dot com 2014-02-10 16:26 ` [Bug middle-end/52306] [4.8/4.9 " law at gcc dot gnu.org 2014-02-19 22:02 ` [Bug middle-end/52306] [4.8 " schwab@linux-m68k.org 2014-02-23 14:21 ` mikpelinux at gmail dot com 2014-05-22 9:07 ` rguenth at gcc dot gnu.org 2014-12-19 13:44 ` jakub at gcc dot gnu.org 2015-01-19 22:34 ` law at redhat 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=bug-52306-4-KoxY6kdcN7@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).