From: Eric Botcazou <ebotcazou@adacore.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Andrew Haley <aph-gcc@littlepinkcloud.com>, gcc-patches@gcc.gnu.org
Subject: Re: Don't set DECL_IGNORED_P on a cdtor function
Date: Sat, 06 Oct 2007 16:04:00 -0000 [thread overview]
Message-ID: <200710061805.43432.ebotcazou@adacore.com> (raw)
In-Reply-To: <20071005151136.GA23184@caradoc.them.org>
> There's two sets of frame information on targets which use DWARF-2
> for exception handling: .debug_frame and .eh_frame. I don't think
> DECL_IGNORED_P should suppress either.
OK, the bottom line is that it doesn't suppress either when they both exist,
e.g. for languages with EH and for targets with DWARF-2 unwind info. It
suppresses the former for targets without DWARF-2 unwind info (VxWorks) or
for languages without EH.
It all boils down to which functions you put DECL_IGNORED_P on. In Ada, we
really want to completely ignore them so .debug_frame is not a problem.
However, given the awkward variability of its effects depending on the target,
I agree that it's probably better to revert the change. Will do shortly.
--
Eric Botcazou
next prev parent reply other threads:[~2007-10-06 16:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 21:23 Geoffrey Keating
2007-10-04 21:36 ` Daniel Jacobowitz
2007-10-04 21:58 ` Eric Botcazou
2007-10-04 22:05 ` Daniel Jacobowitz
2007-10-05 5:57 ` Eric Botcazou
2007-10-04 22:13 ` Geoffrey Keating
2007-10-04 22:55 ` Daniel Jacobowitz
2007-10-05 7:33 ` Eric Botcazou
2007-10-05 8:55 ` Eric Botcazou
2007-10-05 14:47 ` Daniel Jacobowitz
2007-10-05 14:52 ` Andrew Haley
2007-10-05 15:11 ` Daniel Jacobowitz
2007-10-06 16:04 ` Eric Botcazou [this message]
2007-10-07 9:28 ` Eric Botcazou
2007-10-08 22:27 ` Mark Mitchell
2007-10-09 0:18 ` Eric Botcazou
2007-10-09 0:35 ` Mark Mitchell
2007-10-09 4:30 ` Geoffrey Keating
2007-10-09 21:03 ` Mark Mitchell
2007-10-09 21:08 ` Eric Botcazou
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=200710061805.43432.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=aph-gcc@littlepinkcloud.com \
--cc=drow@false.org \
--cc=gcc-patches@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).