From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Merge dg-extract-results.{sh,py} from GCC upstream
Date: Thu, 12 Feb 2015 20:27:00 -0000 [thread overview]
Message-ID: <54DD0C8F.6050303@redhat.com> (raw)
In-Reply-To: <1418686405-29922-1-git-send-email-sergiodj@redhat.com>
On 12/15/2014 11:33 PM, Sergio Durigan Junior wrote:
>
> gdb/testsuite/ChangeLog:
> 2014-12-14 Sergio Durigan Junior <sergiodj@redhat.com>
>
> Merge dg-extract-results.{sh,py} from GCC upstream (r210243,
> r210637, r210913, r211666, r215400, r215817).
>
> 2014-05-08 Richard Sandiford <rdsandiford@googlemail.com>
> * dg-extract-results.py: New file.
Unfortunately, the Python version of this script (dg-extract-results.py)
doesn't produce stable results. The sorting changes between runs for
some reason. That may be tolerable for GCC, but for GDB, it often
renders test diffing unworkable.
I think we should remove dg-extract-results.py, and re-sync
dg-extract-results.sh from the gcc repo to pick up your fix for
the grep/binary issue that went in meanwhile.
WDYT?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-02-12 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 23:33 Sergio Durigan Junior
2014-12-16 0:29 ` Doug Evans
2014-12-16 0:39 ` Sergio Durigan Junior
2015-02-12 20:27 ` Pedro Alves [this message]
2015-02-12 20:32 ` Sergio Durigan Junior
2015-02-12 20:38 ` Pedro Alves
2015-02-12 20:47 ` Sergio Durigan Junior
2015-03-09 17:50 ` Merge 'Make dg-extract-results.sh explicitly treat .{sum,log}, files as text' change (Re: [PATCH] Merge dg-extract-results.{sh,py} from GCC upstream) Pedro Alves
2015-03-09 17:53 ` [pushed] Delete gdb/testsuite/dg-extract-results.py " Pedro Alves
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=54DD0C8F.6050303@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.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