public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph-gcc@littlepinkcloud.COM>
To: Daniel Jacobowitz <drow@false.org>
Cc: Eric Botcazou <ebotcazou@adacore.com>, gcc-patches@gcc.gnu.org
Subject: Re: Don't set DECL_IGNORED_P on a cdtor function
Date: Fri, 05 Oct 2007 14:52:00 -0000	[thread overview]
Message-ID: <18182.20406.270251.74075@zebedee.pink> (raw)
In-Reply-To: <20071005144740.GA20840@caradoc.them.org>

Daniel Jacobowitz writes:
 > On Fri, Oct 05, 2007 at 09:35:18AM +0200, Eric Botcazou wrote:
 > > > I still think there is a problem with omitting .debug_frame though;
 > > > that's more important.
 > > 
 > > I've attached an Ada testcase, which compiles down into 2 functions, the 
 > > second one being DECL_IGNORED_P.  AFAICS .debug_frame contains 2 FDEs.
 > > Is this what you meant by "frame information regardless of DECL_IGNORED_P"?
 > > 
 > > That being said, things might work differently on Darwin.
 > 
 > I'm just going by what Geoff said:
 > 
 >   DECL_IGNORED_P means that there's no DWARF frame information

I'm getting confused here.  I can understand that DECL_IGNORED_P
prevents the emission of debugging frame information, but I assume
that it doesn't prevent the emission of unwinder frame information.

Andrew.

  reply	other threads:[~2007-10-05 14:52 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 [this message]
2007-10-05 15:11         ` Daniel Jacobowitz
2007-10-06 16:04           ` Eric Botcazou
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=18182.20406.270251.74075@zebedee.pink \
    --to=aph-gcc@littlepinkcloud.com \
    --cc=drow@false.org \
    --cc=ebotcazou@adacore.com \
    --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).