public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jie Zhang <jzhang918@gmail.com>
To: dclarke@blastwave.org
Cc: gcc-help@gcc.gnu.org
Subject: Re: Assume testsuite is okay. How do I know that the install result  	is also okay?
Date: Mon, 22 Feb 2010 00:59:00 -0000	[thread overview]
Message-ID: <6f48278f1002192303l55ac9488j4f9b4e1d55c8a25b@mail.gmail.com> (raw)
In-Reply-To: <48695.10.0.66.17.1266299093.squirrel@interact.purplecow.org>

On Tue, Feb 16, 2010 at 1:44 PM, Dennis Clarke <dclarke@blastwave.org> wrote:
>
> This may seem like an odd question but I have spent some time looking at
> this and wondering.
>
> Assume that I have performed a full three stage bootstrap and then ran the
> testsuite. Assume that I was happy with the results and then ran the
> install.
>
> How do I know that the resultant compiler that is now in the --prefix=dir
> is also complete and "okay" ?
>
> The testsuite was run while the present working dir was the objdir.
> However after install we assume that everything lands correctly in the
> destination. Can we also run the testsuite *after* install and only with
> the compiler in the final install location?
>
Yes. You can take a look at test_gcc in the following file:

http://blackfin.uclinux.org/gf/project/toolchain/scmsvn/?action=browse&path=%2Ftrunk%2Fbuildscript%2Ftoolchain-regtest&view=markup&revision=3942

Jie

      reply	other threads:[~2010-02-20  7:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  8:15 Dennis Clarke
2010-02-22  0:59 ` Jie Zhang [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=6f48278f1002192303l55ac9488j4f9b4e1d55c8a25b@mail.gmail.com \
    --to=jzhang918@gmail.com \
    --cc=dclarke@blastwave.org \
    --cc=gcc-help@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).