public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stevenb.gcc at gmail dot com" <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:42:00 -0000	[thread overview]
Message-ID: <bug-56858-4-8GdtsZGfpm@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 #10 from stevenb.gcc at gmail dot com <stevenb.gcc at gmail dot com> 2013-04-08 19:42:51 UTC ---
> 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 barely know a thing about EH, or IEEE exceptions, let alone a
combination or two. I'm a doc^Wn aerospace engineer, not a computer
scientist.

> 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.

Removing the notes entirely is the goal eventually, but I'd settle for
making them local to final.c for now.

What besides alpha and final are keeping these notes alive? You've
probably seen my grep results, and at least from passes.c there
doesn't seem to be anything between pass_convert_to_eh_region_ranges
and pass_final that would use the INSN_NOTEs:

          NEXT_PASS (pass_convert_to_eh_region_ranges);
          NEXT_PASS (pass_shorten_branches);
          NEXT_PASS (pass_set_nothrow_function_flags);
          NEXT_PASS (pass_dwarf2_frame);
          NEXT_PASS (pass_final);

AFAIU the only code transformations done in these passes are in
shorten_branches that shouldn't care whether it's dealing with the
REG_EH_REGION notes or the NOTE_INSN_EH_REGION notes.

But my U in AFAIU is obviously no-where near your U when it comes to
EH, so if you can explain a bit, I'd really appreciate it! :-)

(On the topic of notes: note to self, kill NOTE_EH_CONTEXT.)


  parent reply	other threads:[~2013-04-08 19:42 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
2013-04-08 19:42 ` stevenb.gcc at gmail dot com [this message]
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-8GdtsZGfpm@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: link
Be 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).