public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org, rdsandiford@googlemail.com
Subject: Re: RFA: speeding up dg-extract-results.sh
Date: Mon, 05 May 2014 16:08:00 -0000	[thread overview]
Message-ID: <5367B76D.4060200@redhat.com> (raw)
In-Reply-To: <878utfe5g0.fsf@talisman.default>

On 02/13/14 02:18, Richard Sandiford wrote:
>
>      http://gcc.gnu.org/ml/gcc-testresults/2014-02/msg00025.html
>
> the script takes just over 5 hours to produce the gcc.log file.
Good grief...

>
> This patch tries to reduce that by providing an alternative single-script
> version.  I was torn between Python and Tcl, but given how most people
> tend to react to Tcl, I thought I'd better go for Python.  I wouldn't
> mind rewriting it in Tcl if that seems better though, not least because
> expect is already a prerequisite.
Can't argue with that reasoning.  There's been talk of rewriting the 
testsuite drivers to use python rather than tcl under the hood.  I'd be 
surprised if anyone in our community really prefers tcl over python.

It would mean a bit of pain for initial system bootstraps by the 
distributors, but those are relatively rare occurrences and they can 
always seed that process by building without testing to get the initial 
tools, when are then used to build python, then rebuild gcc to get the 
testing done.  I don't see this as being a major issue.


>
> Python isn't yet required and I'm pretty sure this script needs 2.6
> or later.  I'm also worried that the seek/tell stuff might not work on
> Windows.  The patch therefore gets dg-extract-results.sh to check the
> environment first and call into the python version if possible,
> otherwise it falls back on the current approach.  This also means
> that the patch is contained entirely within contrib/.  If this does
> indeed not work on Windows then we should either fix the python code
> (obviously preferred) or get dg-extract-results.sh to skip it on
> Windows for now.
Kai can probably test an answer questions about the Windows space.

> I checked that the outputs were otherwise identical for a set of
> mips64-linux-gnu, mipsisa64-sde-elf and x86_64-linux-gnu runs.  I also
> reran the acats tests with some nobbled testcases in order to test the
> failure paths there.
>
> Also bootstrapped & regression-tested on x86_64-linux-gnu.  OK to install?

>
> Thanks,
> Richard
>
>
> contrib/
> 	* dg-extract-results.py: New file.
> 	* dg-extract-results.sh: Use it if the environment seems suitable.
OK by me.

jeff

  parent reply	other threads:[~2014-05-05 16:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13  9:18 Richard Sandiford
2014-05-03  7:34 ` Ping: " Richard Sandiford
2014-05-05 19:17   ` Jakub Jelinek
2014-05-05 20:36     ` Richard Sandiford
2014-05-03 20:07 ` Mike Stump
2014-05-05 16:08 ` Jeff Law [this message]
2014-05-05 18:15   ` Mike Stump
2014-05-05 18:16     ` Jeff Law
     [not found] ` <CADnVucCA0ozSz=x3z8vexBOkWRj3pquKVuWsFq4xZre0CfxFyQ@mail.gmail.com>
2014-05-19 18:07   ` Richard Sandiford
2014-05-19 18:49     ` Charles Baylis
2014-05-20 10:09       ` Richard Sandiford
2014-05-24 11:17 ` Bernd Schmidt
2014-05-24 17:15   ` Mike Stump
2014-05-24 17:53     ` Trevor Saunders
2014-05-25  9:35   ` Richard Sandiford
2014-06-12 15:53     ` Bernd Schmidt
2014-06-12 16:32       ` Mike Stump
2014-06-14  9:50       ` Richard Sandiford

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=5367B76D.4060200@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rdsandiford@googlemail.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).