public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nicolas Noble <pixel.nobis@gmail.com>
To: gcc@gcc.gnu.org
Subject: Running gcc testsuite outside of gcc's sourcetree.
Date: Sun, 20 Sep 2009 00:15:00 -0000	[thread overview]
Message-ID: <a70244740909191714w17fa654av51aed38fb606b0aa@mail.gmail.com> (raw)

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.

  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.

  Now only one of these bugs bit me, and bit me hard, and that's how I
discovered the whole thing. I manually ran a bunch of the testcases in
the gcc testsuite, and I already found 15 bugs active there. But
running of all them by hand is difficult and painful, but I don't see
how to do that automatically on the system's compiler from the
testsuite's documentation. My ultimate goal is to evaluate to which
extend I can trust this compiler, and use these results to convince my
management that we're most probably going to face a lot more trouble
if we continue using a compiler that's containing known bugs.

  Is it possible to run the testsuite on the system's compiler ? I've
seen that some of the testcases might not be relevant as they're
trying to check some of gcc's new features that might not be in that
old version. Or would there be another, simpler testsuite I could run
natively ?

  Thanks!

  -- Nicolas Noble

             reply	other threads:[~2009-09-20  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-20  0:15 Nicolas Noble [this message]
2009-09-20  0:51 ` Dave Korn
2009-09-20  3:37 ` Jeff Law

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=a70244740909191714w17fa654av51aed38fb606b0aa@mail.gmail.com \
    --to=pixel.nobis@gmail.com \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).