Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/DWARF2] Handle nested subprograms in CU pc bound 	calculation
Date: Tue, 30 Sep 2008 15:43:00 -0000	[thread overview]
Message-ID: <20080930154235.GA13221@caradoc.them.org> (raw)
In-Reply-To: <20080930152757.GC23135@adacore.com>

On Tue, Sep 30, 2008 at 08:27:57AM -0700, Joel Brobecker wrote:
> Here is what happens:
> 
>   1. When compiling with -ffunction-sections, the compiler is not
>      providing the CU PC bounds (DW_AT_low_pc and DW_AT_high_pc).
>      I would imagine that this is because functions might be removed
>      later during the link, and thus bounds might be affected.

It should provide DW_AT_ranges instead.  Is it not doing that?  What
era compiler is this?

The patch is fine, either way.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-09-30 15:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 15:28 Joel Brobecker
2008-09-30 15:43 ` Daniel Jacobowitz [this message]
2008-09-30 16:56   ` Joel Brobecker
2008-09-30 17:05     ` Daniel Jacobowitz
2008-09-30 15:43 ` Pierre Muller
2008-09-30 17:07   ` Joel Brobecker
2008-09-30 17:39     ` Daniel Jacobowitz
2008-10-01  1:16       ` Joel Brobecker
2008-10-01  7:43         ` Pierre Muller
2008-10-01  8:33           ` [Core] " Jonas Maebe
2008-10-01 16:40           ` Joel Brobecker
2008-10-01 21:56             ` [Core] " Jonas Maebe
2008-10-02  6:45             ` Daniël Mantione
2008-10-02  9:07               ` Pierre Muller
2008-10-02 10:36                 ` Daniël Mantione
2008-10-03  0:31                   ` Joel Brobecker
2008-09-30 16:58 ` Joel Brobecker

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=20080930154235.GA13221@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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