linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/2] normalize bb's label names for testing
Date: Mon, 21 Nov 2016 05:14:19 +0100	[thread overview]
Message-ID: <20161121041421.34576-1-luc.vanoostenryck@gmail.com> (raw)

These two patches solves the testing problem of the label names
as emitted by test-linearize and others being not comparable
between runs.

Luc Van Oostenryck (2):
  testsuite: allow commands to use pipes
  testsuite: add a script to normalize label names

 validation/normalize-bb        | 16 ++++++++++++++++
 validation/test-normalize-bb.c | 31 +++++++++++++++++++++++++++++++
 validation/test-pipe-cmd.c     | 13 +++++++++++++
 validation/test-suite          |  6 +++---
 4 files changed, 63 insertions(+), 3 deletions(-)
 create mode 100755 validation/normalize-bb
 create mode 100644 validation/test-normalize-bb.c
 create mode 100644 validation/test-pipe-cmd.c

-- 
2.10.2


             reply	other threads:[~2016-11-21  4:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21  4:14 Luc Van Oostenryck [this message]
2016-11-21  4:14 ` [PATCH 1/2] testsuite: allow commands to use pipes Luc Van Oostenryck
2016-11-21  4:14 ` [PATCH 2/2] testsuite: add a script to normalize label names Luc Van Oostenryck
2016-11-22 10:02 ` [PATCH 0/2] normalize bb's label names for testing Christopher Li
2016-11-22 13:27   ` Luc Van Oostenryck
2016-11-22 16:44     ` Christopher Li
2016-11-22 17:02       ` Luc Van Oostenryck
2016-11-22 15:42   ` [PATCH] give comparable label's names to basic blocks Luc Van Oostenryck

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=20161121041421.34576-1-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.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 NNTP newsgroup(s).