public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/56858] alpha looks for NOTE_INSN_EH_REGION notes that cannot exist Date: Mon, 08 Apr 2013 19:27:00 -0000 [thread overview] Message-ID: <bug-56858-4-JrD0t1k964@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56858-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56858 --- Comment #9 from Richard Henderson <rth at gcc dot gnu.org> 2013-04-08 19:27:03 UTC --- (In reply to comment #8) > The part of alpha EH that depends on the notes must have been been > broken since than, more than 12 years. Without anyone noticing... Sure. Do you know any package that combines C++ EH with IEEE exceptions? I don't. In fact, I don't actually know of a package that wants to enable trapping fp math at all. > I really, really wouldn't like to keep this code in alpha alive, and > with it these REG_EH_REGION notes, for barely (if at all) used ages-old > alpha targets... Do you believe that you're going to be able to delete the notes entirely, and that it's only Alpha that's keeping them alive? That's certainly not true, I assure you.
next prev parent reply other threads:[~2013-04-08 19:27 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-06 18:07 [Bug target/56858] New: " steven at gcc dot gnu.org 2013-04-06 18:09 ` [Bug target/56858] " steven at gcc dot gnu.org 2013-04-06 21:56 ` steven at gcc dot gnu.org 2013-04-07 8:28 ` ubizjak at gmail dot com 2013-04-08 7:38 ` ubizjak at gmail dot com 2013-04-08 14:35 ` rth at gcc dot gnu.org 2013-04-08 15:32 ` steven at gcc dot gnu.org 2013-04-08 15:52 ` rth at gcc dot gnu.org 2013-04-08 18:43 ` steven at gcc dot gnu.org 2013-04-08 19:27 ` rth at gcc dot gnu.org [this message] 2013-04-08 19:42 ` stevenb.gcc at gmail dot com 2013-04-08 20:09 ` rth at gcc dot gnu.org 2013-04-21 21:15 ` ubizjak at gmail dot com 2013-04-21 21:36 ` stevenb.gcc at gmail dot com 2014-06-26 10:15 ` ubizjak at gmail dot com 2014-06-26 10:17 ` ubizjak at gmail dot com 2014-07-11 7:43 ` uros at gcc dot gnu.org 2014-07-14 14:09 ` ubizjak at gmail 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-56858-4-JrD0t1k964@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).