Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Ada testsuite failures
Date: Tue, 02 Jan 2007 14:42:00 -0000	[thread overview]
Message-ID: <20070102144205.GB10771@nevyn.them.org> (raw)
In-Reply-To: <20070102073827.GB3434@adacore.com>

On Tue, Jan 02, 2007 at 11:38:27AM +0400, Joel Brobecker wrote:
> I wouldn't be surprised. Recents versions of GCC are much better at
> not emitting debugging info for unused entity. This has caused us a lot
> of trouble when moving to GCC 4.1 for instance, because GNAT generates
> of lot of entities that appear unused from the compiler point of view,
> but are necessary for the debugger to work properly. We're getting back
> to the same project of getting rid of all these encoding in favor of
> standard DWARF. This is actually a very active project that we're
> working on right now, so hopefully the situation won't be as bad soon.

The unused type purging does sound like a likely culprit for these,
yeah.  Just adding -fno-eliminate-unused-debug-types doesn't fix it,
but it's probably related.

> I can ask that the local patches we maintain in our tree be submitted
> for inclusion if you think they'd be accepted. Our opinion was that they
> would probably be rejected as a step backward.

Well, I'd like to see them, anyway.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-01-02 14:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-31 19:46 Daniel Jacobowitz
2007-01-02  7:37 ` Joel Brobecker
2007-01-02 14:42   ` Daniel Jacobowitz [this message]
2007-01-02 16:31     ` Joel Brobecker
2007-01-02 11:38 ` Joel Brobecker
2007-01-02 14:39   ` Daniel Jacobowitz
2007-01-02 16:30     ` Joel Brobecker
2007-01-02 16:32       ` Joel Brobecker
2007-01-02 16:40         ` Daniel Jacobowitz
2007-01-02 16:50           ` Joel Brobecker
2007-01-03 14:04           ` Joel Brobecker
2007-01-03 14:05             ` Joel Brobecker
2007-01-03 22:21             ` Jim Blandy

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=20070102144205.GB10771@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@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