From: Joel Brobecker <brobecker@adacore.com>
To: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: arrayidx.exp failures
Date: Fri, 13 Oct 2006 16:34:00 -0000 [thread overview]
Message-ID: <20061013163352.GJ1059@adacore.com> (raw)
In-Reply-To: <20061013043855.GA28303@nevyn.them.org>
> FYI, Joel, I have no idea what compilers you test with - but half of
> the Ada tests in the GDB testsuite have never passed for me with FSF
> gnat, at least 4.0 and 4.1, and possibly 3.4 too.
It's good you told me, I will try to talk to some of my collegues
who work on the compiler and see where we are.
I use exclusively GNAT Pro, which is the compiler we maintain at
AdaCore. Right now, it's based on GCC 3.4.6, but are actively moving
to a GCC 4.1 backend on most of our platforms. That's when we found
a lot of issues in debug info generation that apparently appear only
with Ada - we have fixed several of them and I believe that they have
been submitted although I will admit that I do not follow compiler
work very closely.
If I started doing my testing with various flavours of GCC, the number
of combinations would explode. I already run our in-house testsuite (not
based on dejagnu) together with the GDB testsuite, both with our
GDB tree and the FSF head.
All I can say is that we're getting better at pushing our changes
to the FSF tree both on the GCC side as well as the GDB side, but
it's a slow process because first we have to catch up and then we
have to learn how to best do it.
In the meantime, are these fails an issue? For me, I have the same sort
of issue in a smaller scale with C++ testcases, but the way I test is
by using a smart-diff between the testcase results before and after.
--
Joel
next prev parent reply other threads:[~2006-10-13 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 2:17 Nick Roberts
2006-10-13 2:38 ` Joel Brobecker
2006-10-13 4:39 ` Daniel Jacobowitz
2006-10-13 16:34 ` Joel Brobecker [this message]
2006-10-13 18:50 ` Nick Roberts
2006-10-13 20:10 ` Joel Brobecker
2006-10-13 22:06 ` Daniel Jacobowitz
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=20061013163352.GJ1059@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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