From: Mike Stump <mikestump@comcast.net>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PING, PATCH, testsuite] Reliably prune GCC notes in C++ compat suite
Date: Wed, 23 Jul 2014 22:17:00 -0000 [thread overview]
Message-ID: <453904D4-D812-4633-9E45-9420912A7FD6@comcast.net> (raw)
In-Reply-To: <201407231142.s6NBgXCD019089@d06av02.portsmouth.uk.ibm.com>
On Jul 23, 2014, at 4:42 AM, Ulrich Weigand <uweigand@de.ibm.com> wrote:
> Ping?
Ok.
>> Hello,
>>
>> in testing the rs6000 ABI patches I noted a weird effect: usually, the
>> -Wpsabi warning notes are ignored in the compat test suites, so we get
>> a clean test run anyway.
>>
>> However, when running the C++ version of the struct-layout-1.exp case
>> *alone* (using RUNTESTFLAGS=struct-layout-1.exp), suddenly tests are
>> failing because of those extra notes. This does *not* happen with
>> the C version of that suite ...
>>
>> It turns out that that pruning those notes is supposed to happen
>> from within gcc-defs.exp:${tool}_check_compile:
>> if { [info proc ${tool}-dg-prune] != "" } {
>> global target_triplet
>> set gcc_output [${tool}-dg-prune $target_triplet $gcc_output]
>> }
>>
>> However, the g++-dg-prune routine is defined in g++-dg.exp, which
>> is never included from g++.dg/compat/struct-layout-1.exp (directly
>> or indirectly). Now, when running the full suite, that file would
>> have been loaded by some earlier g++.dg .exp file, so everything
>> works out. But when running struct-layout-1.exp stand-alone, the
>> g++-dg-prune routine is never defined and thus silently no pruning
>> takes place.
>>
>> To fix this, the following patch simply loads g++-dg.exp directly
>> from g++.dg/compat/struct-layout-1.exp.
>>
>> Tested on powerpc64-linux and powerpc64le-linux.
>>
>> OK for mainline (and 4.8/4.9 once the rs6000 ABI patches are
>> backported there)?
>>
>> Bye,
>> Ulrich
>>
>>
>> gcc/testsuite/ChangeLog:
>>
>> * g++.dg/compat/struct-layout-1.exp: Load g++-dg.exp
>>
>>
>> Index: gcc-4_9-branch/gcc/testsuite/g++.dg/compat/struct-layout-1.exp
>> ===================================================================
>> --- gcc-4_9-branch.orig/gcc/testsuite/g++.dg/compat/struct-layout-1.exp
>> +++ gcc-4_9-branch/gcc/testsuite/g++.dg/compat/struct-layout-1.exp
>> @@ -89,6 +89,9 @@ proc compat-use-tst-compiler { } {
>> # This must be done after the compat-use-*-compiler definitions.
>> load_lib compat.exp
>>
>> +# Provide the g++-dg-prune routine (gcc-dp.exp is loaded by compat.exp)
>> +load_lib g++-dg.exp
>> +
>> g++_init
>>
>> # Save variables for the C++ compiler under test, which each test will
>>
>> --
>> Dr. Ulrich Weigand
>> GNU/Linux compilers and toolchain
>> Ulrich.Weigand@de.ibm.com
>>
>
>
> --
> Dr. Ulrich Weigand
> GNU/Linux compilers and toolchain
> Ulrich.Weigand@de.ibm.com
>
prev parent reply other threads:[~2014-07-23 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 2:25 [PATCH, " Ulrich Weigand
2014-07-17 16:14 ` Bernhard Reutner-Fischer
2014-07-23 11:52 ` [PING, PATCH, " Ulrich Weigand
2014-07-23 22:17 ` Mike Stump [this message]
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=453904D4-D812-4633-9E45-9420912A7FD6@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=uweigand@de.ibm.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).