Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Merge dg-extract-results.{sh,py} from GCC upstream
Date: Tue, 16 Dec 2014 00:29:00 -0000	[thread overview]
Message-ID: <CADPb22SPJ8DhdGOjZPZz=Mw3y+CSxGHKo5aLdKDqRf4H0y9YmA@mail.gmail.com> (raw)
In-Reply-To: <1418686405-29922-1-git-send-email-sergiodj@redhat.com>

On Mon, Dec 15, 2014 at 3:33 PM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> It has been a while since we don't sync this file with GCC upstream,
> and in the meantime some interesting things have happened.  The most
> interesting is the inclusion of a new dg-extract-results.py which is
> apparently faster than its shell equivalent.
>
> This merge will probably fix the bug described in
>
>   <https://sourceware.org/ml/gdb-patches/2014-12/msg00421.html>
>
> Though I am still proposing the patch for upstream GCC.  Once it gets
> accepted, I will merge it too.
>
> OK to apply?
>
> 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.
>                 * dg-extract-results.sh: Use it if the environment seems
>                 suitable.
>
>         2014-05-20  Richard Sandiford  <rdsandiford@googlemail.com>
>
>                 * dg-extract-results.py (parse_run): Handle warnings that
>                 are printed before a test harness is run.
>
>         2014-05-25  Richard Sandiford  <rdsandiford@googlemail.com>
>
>                 * dg-extract-results.py (Named): Remove __cmp__ method.
>                 (output_variation): Use a key to sort variation.harnesses.
>
>         2014-06-14  Richard Sandiford  <rdsandiford@googlemail.com>
>
>                 * dg-extract-results.py: For Python 3, force sys.stdout to
>                 handle surrogate escape sequences.
>                 (safe_open): New function.
>                 (output_segment, main): Use it.
>
>         2014-09-19  Segher Boessenkool  <segher@kernel.crashing.org>
>
>                 * dg-extract-results.py (Prog.result_re): Include options
>                 in test name.
>
>         2014-10-02  Segher Boessenkool  <segher@kernel.crashing.org>
>
>                 * dg-extract-results.py (output_variation): Always sort if
>                 do_sum.

Ok by me.


  reply	other threads:[~2014-12-16  0:29 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 [this message]
2014-12-16  0:39   ` Sergio Durigan Junior
2015-02-12 20:27 ` Pedro Alves
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='CADPb22SPJ8DhdGOjZPZz=Mw3y+CSxGHKo5aLdKDqRf4H0y9YmA@mail.gmail.com' \
    --to=dje@google.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