From: "Martin Liška" <mliska@suse.cz>
To: Renlin Li <renlin.li@foss.arm.com>, Jakub Jelinek <jakub@redhat.com>
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
Uros Bizjak <ubizjak@gmail.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Richard Guenther <richard.guenther@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Come up with gcc/testsuite/g++.target/i386/i386.dg and move there some tests.
Date: Tue, 20 Nov 2018 12:08:00 -0000 [thread overview]
Message-ID: <0a1b2518-bda9-c8e0-2f45-d23acfb60eb5@suse.cz> (raw)
In-Reply-To: <d6f67f8d-9ee2-d05f-f470-795823a9537f@foss.arm.com>
On 11/16/18 6:01 PM, Renlin Li wrote:
> Hi Martin,
>
> Seems the change is not checked in yet?
Sorry, I've just installed the patch.
Martin
>
> Thanks,
> Renlin
>
> On 10/22/2018 01:22 PM, Martin Liška wrote:
>> On 10/22/18 12:09 PM, Jakub Jelinek wrote:
>>> On Mon, Oct 22, 2018 at 12:04:23PM +0200, Martin Liška wrote:
>>>>> I noticed that before the tests were run with all of
>>>>> -std=(c|gnu)++(98|11|14), now with no explict -std option. I wonder if
>>>>> this is an issue.
>>>>>
>>>>> Â Â Â Â Rainer
>>>>>
>>>>
>>>> Hello.
>>>>
>>>> I guess that should not be a problem.
>>>
>>> If we want that, it is a matter of (untested):
>>> --- gcc/testsuite/g++.target/i386/i386.exp.jj   2018-10-10 10:50:48.352235231 +0200
>>> +++ gcc/testsuite/g++.target/i386/i386.exp   2018-10-22 12:08:56.546807996 +0200
>>> @@ -35,8 +35,8 @@ dg-init
>>> Â clearcap-init
>>> Â Â # Main loop.
>>> -dg-runtest [lsort [glob -nocomplain $srcdir/$subdir/*.C]] \
>>> -Â Â Â Â Â Â Â "" $DEFAULT_CXXFLAGS
>>> +g++-dg-runtest [lsort [glob -nocomplain $srcdir/$subdir/*.C]] \
>>> +Â Â Â Â Â Â Â Â Â Â "" $DEFAULT_CXXFLAGS
>>> Â Â # All done.
>>> Â clearcap-finish
>>>
>>> Â Â Â Â Jakub
>>>
>>
>> Thank you Jakub, works for me for:
>> $ make check -k RUNTESTFLAGS="i386.exp"
>>
>> I can confirm that:
>> grep '^PASS' ./gcc/testsuite/g++/g++.log | wc -l
>>
>>
>> changed from 61 to 183.
>>
>> I'm going to install the patch.
>>
>> Martin
>>
>>
prev parent reply other threads:[~2018-11-20 12:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 14:12 [PATCH] Redirect call within specific target attribute among MV clones (PR ipa/82625) Martin Liška
2018-10-04 14:34 ` Jeff Law
2018-10-04 14:58 ` Martin Liška
2018-10-08 9:16 ` Renlin Li
2018-10-08 10:06 ` Martin Liška
2018-10-08 10:11 ` Richard Earnshaw (lists)
2018-10-08 10:29 ` Martin Liška
2018-10-08 10:34 ` Richard Biener
2018-10-08 10:46 ` Martin Liška
2018-10-08 10:55 ` Jakub Jelinek
2018-10-08 11:01 ` Martin Liška
2018-10-08 11:14 ` Richard Earnshaw (lists)
2018-10-08 11:29 ` [PATCH] Come up with gcc/testsuite/g++.target/i386/i386.dg and move there some tests Martin Liška
2018-10-08 11:33 ` Jakub Jelinek
2018-10-08 11:47 ` Uros Bizjak
2018-10-08 12:49 ` Martin Liška
2018-10-08 13:21 ` Uros Bizjak
2018-10-09 9:52 ` Martin Liška
2018-10-09 10:06 ` Rainer Orth
2018-10-09 11:44 ` Martin Liška
2018-10-12 9:27 ` Rainer Orth
2018-10-22 10:24 ` Martin Liška
2018-10-22 10:31 ` Jakub Jelinek
2018-10-22 13:08 ` Martin Liška
2018-11-16 17:01 ` Renlin Li
2018-11-20 12:08 ` Martin Liška [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=0a1b2518-bda9-c8e0-2f45-d23acfb60eb5@suse.cz \
--to=mliska@suse.cz \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=renlin.li@foss.arm.com \
--cc=richard.guenther@gmail.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=ubizjak@gmail.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).