From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: Re: New Ada failure
Date: Fri, 05 Jan 2007 16:03:00 -0000 [thread overview]
Message-ID: <20070105160431.GA14740@adacore.com> (raw)
In-Reply-To: <20070105154157.GA26403@nevyn.them.org>
> > I have now checked in a patch in GCC that explains that the GNAT
> > runtime should not be stripped. Would you mind filing a bug with
> > the Debian maintainers? I'm not familiar with the procedure. You
> > may want to mention to them that they should be able to build the
> > runtime without -g. There is a flag for it, probably LIBGNATCFLAGS
> > or some such. The makefiles will know to force -g -O1 for the few
> > units we need.
>
> Done, though we may take a different approach. Meanwhile, should
> we let the test fail for this case, or mark it UNSUPPORTED?
I am of two hearts with this. On the one hand, yes, the test should
be unsupported if the GNAT runtime is malformed. However, a bug in
our lookup would yield the same type of failure, and thus marking
the testcase as unsuported would hide that.
I would lean towards making it UNSUPPORTED, since the chances of
the lookup failing are fairly remote (or many other testcases
will badly fail).
If we decide to make it unsupported, would you mind taking care of it?
I cannot reproduce your problem, and my attempts at building the FSF
compiler from sources have miserably failed...
Thank you,
--
Joel
prev parent reply other threads:[~2007-01-05 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 20:24 Daniel Jacobowitz
2007-01-04 23:09 ` Robert Dewar
2007-01-04 23:15 ` Daniel Jacobowitz
2007-01-04 23:22 ` Mark Kettenis
2007-01-04 23:26 ` Robert Dewar
2007-01-04 23:27 ` Daniel Jacobowitz
2007-01-05 3:56 ` Joel Brobecker
2007-01-05 3:59 ` Daniel Jacobowitz
2007-01-05 4:06 ` Joel Brobecker
2007-01-05 15:31 ` Joel Brobecker
2007-01-05 15:42 ` Daniel Jacobowitz
2007-01-05 16:03 ` Joel Brobecker [this message]
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=20070105160431.GA14740@adacore.com \
--to=brobecker@adacore.com \
--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