From: Jeff Law <law@redhat.com>
To: Nicolas Noble <pixel.nobis@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Running gcc testsuite outside of gcc's sourcetree.
Date: Sun, 20 Sep 2009 03:37:00 -0000 [thread overview]
Message-ID: <4AB5A374.5080804@redhat.com> (raw)
In-Reply-To: <a70244740909191714w17fa654av51aed38fb606b0aa@mail.gmail.com>
On 09/19/09 18:14, Nicolas Noble wrote:
> Hello,
>
> Long story short, I'm looking for a way to test a distribution's
> compiler by running the latest gcc testsuite on it, but so far, I've
> only seem to run it on the same gcc sourcetree it's on. I actually
> wonder if it's possible and/or relevant to do this on the
> distribution's compiler.
>
It's certainly possible. Under the hood the Makefile just invokes
runtest. I don't think people do this that often anymore, so you might
have to set some environment variables and/or set some paths, but when
it's all said and done you can probably do something like
cd <gcc sources>/gcc/testsuite
runtest --tool=gcc
runtest --tool=g++
Which should run the gcc & g++ testsuites with your system compiler.
> My problem resides in RedHat's gcc (which version seems to be gcc
> (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42)). I recently discovered that
> this compiler hosts a bunch of known gcc bugs that have been reported
> and fixed in the gcc mainstream, but it seems the bugfixes never got
> ported back in RedHat's.
>
The fact of the matter is that every compiler has bugs. Backporting
every bugfix to old releases isn't practical, particularly if the fix
has the potential to introduce new regressions. It's a balancing act
our engineers deal with daily. Customers (of course) have input into
how we balance those decisions, and if you are a customer I would
strongly encourage you to file a bug report with Red Hat.
Jeff
prev parent reply other threads:[~2009-09-20 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 0:15 Nicolas Noble
2009-09-20 0:51 ` Dave Korn
2009-09-20 3:37 ` Jeff Law [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=4AB5A374.5080804@redhat.com \
--to=law@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pixel.nobis@gmail.com \
/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).