public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/28282] Attempt to delete prologue/epilogue insn, again Date: Fri, 07 Jul 2006 09:53:00 -0000 [thread overview] Message-ID: <20060707095233.3017.qmail@sourceware.org> (raw) In-Reply-To: <bug-28282-12916@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from rguenth at gcc dot gnu dot org 2006-07-07 09:52 ------- The question is why we need to ICE here. We may as well go ahead and pretend it was the users fault and not a bug in some previous pass... -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- BugsThisDependsOn| |12535 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28282
next prev parent reply other threads:[~2006-07-07 9:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-06 9:27 [Bug rtl-optimization/28282] New: " ted at midg3t dot net 2006-07-06 9:29 ` [Bug rtl-optimization/28282] " ted at midg3t dot net 2006-07-06 9:29 ` ted at midg3t dot net 2006-07-06 9:35 ` ted at midg3t dot net 2006-07-07 9:45 ` [Bug target/28282] " rguenth at gcc dot gnu dot org 2006-07-07 9:46 ` rguenth at gcc dot gnu dot org 2006-07-07 9:53 ` rguenth at gcc dot gnu dot org [this message] 2006-07-08 4:48 ` pinskia at gcc dot gnu dot org 2007-07-25 19:01 ` pinskia 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=20060707095233.3017.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).