From: Richard Biener <richard.guenther@gmail.com>
To: Mike Stump <mikestump@comcast.net>
Cc: Pierre-Marie de Rodat <derodat@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/2] Python testcases to check DWARF output
Date: Thu, 27 Jul 2017 07:52:00 -0000 [thread overview]
Message-ID: <CAFiYyc1JEHOrP8VscT0_JPYmCFAd_Ob733NN9T4+Oe_AETxmOw@mail.gmail.com> (raw)
In-Reply-To: <8EF1EAAC-B956-4214-A707-EE692659F428@comcast.net>
On Wed, Jul 26, 2017 at 11:25 PM, Mike Stump <mikestump@comcast.net> wrote:
> On Jul 26, 2017, at 9:00 AM, Pierre-Marie de Rodat <derodat@adacore.com> wrote:
>> At the last GNU Cauldron, Richard Biener and I talked about DWARF output
>> testing. Except for guality tests, which are disabled on several
>> targets, the only way tests check the DWARF is scanning the annotated
>> assembly (-dA), making it hard to write reliable tests.
>
>> Anyway, Richard and I discussed about doing something similar in-tree,
>> and here is a candidate set of patches to achieve that
>
> I'm fine with the direction if a reviewer wants to go in that direction. I wish python didn't have a built-in speed penalty, that's the only downside I don't like about it. Aside from that, even switching all of the testsuite to be python based isn't a terrible idea.
But is it worse than TCL?
Richard.
next prev parent reply other threads:[~2017-07-27 7:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 16:01 Pierre-Marie de Rodat
2017-07-26 16:01 ` [PATCH 2/2] Introduce " Pierre-Marie de Rodat
2017-07-26 17:10 ` David Malcolm
2017-07-27 8:59 ` Pierre-Marie de Rodat
2017-07-27 8:36 ` Richard Biener
2017-07-27 10:09 ` Pierre-Marie de Rodat
2017-07-26 16:01 ` [PATCH 1/2] Introduce testsuite support to run Python tests Pierre-Marie de Rodat
2017-07-26 16:25 ` David Malcolm
2017-07-26 16:35 ` Pierre-Marie de Rodat
2017-07-26 16:48 ` David Malcolm
2017-07-27 8:49 ` Pierre-Marie de Rodat
2017-07-27 13:40 ` David Malcolm
2017-08-02 18:43 ` Jeff Law
2017-08-03 8:27 ` Pierre-Marie de Rodat
2017-07-27 8:50 ` Matthias Klose
2017-07-27 10:09 ` Pierre-Marie de Rodat
2017-07-26 16:16 ` [PATCH 0/2] Python testcases to check DWARF output David Malcolm
2017-07-26 16:26 ` Pierre-Marie de Rodat
2017-07-26 21:25 ` Mike Stump
2017-07-27 7:52 ` Richard Biener [this message]
2017-07-27 9:09 ` Pierre-Marie de Rodat
2017-08-03 22:23 ` Mike Stump
2017-08-06 14:35 ` Iain Buclaw
2017-08-02 15:44 ` Jeff Law
2017-08-02 15:43 ` Jeff Law
2017-08-03 8:27 ` Pierre-Marie de Rodat
2017-08-03 16:13 ` 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=CAFiYyc1JEHOrP8VscT0_JPYmCFAd_Ob733NN9T4+Oe_AETxmOw@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=derodat@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).