From: "Martin Liška" <mliska@suse.cz>
To: Richard Biener <richard.guenther@gmail.com>, indu.bhagat@oracle.com
Cc: Martin Sebor <msebor@gmail.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR86957
Date: Thu, 27 Sep 2018 10:15:00 -0000 [thread overview]
Message-ID: <ad8f6aed-869b-1187-3da4-8dfe038beafb@suse.cz> (raw)
In-Reply-To: <CAFiYyc2tRw4GxYXv_ReFQAed2oVsovyePdegUdnjy4Ly4L0T4w@mail.gmail.com>
On 9/27/18 11:47 AM, Richard Biener wrote:
> On Mon, Sep 24, 2018 at 9:14 PM Indu Bhagat <indu.bhagat@oracle.com> wrote:
>>
>> Done. Attached is updated patch.
>>
>> Patch is tested on x86_64
>
> You obviously did _not_ properly test the patch since it causes a
> bunch of new testsuite
> failures:
>
> FAIL: g++.dg/pr60518.C -std=gnu++11 (test for excess errors)
> FAIL: g++.dg/pr60518.C -std=gnu++14 (test for excess errors)
> FAIL: g++.dg/pr60518.C -std=gnu++98 (test for excess errors)
> FAIL: g++.dg/tree-ssa/dom-invalid.C -std=gnu++11 (test for excess errors)
> FAIL: g++.dg/tree-ssa/dom-invalid.C -std=gnu++14 (test for excess errors)
> FAIL: g++.dg/tree-ssa/dom-invalid.C -std=gnu++98 (test for excess errors)
> FAIL: g++.dg/guality/pr55665.C -O2 -flto -fno-use-linker-plugin
> -flto-partition=none line 23 p == 40
> FAIL: g++.dg/torture/pr59265.C -O0 (test for excess errors)
> FAIL: g++.dg/torture/pr59265.C -O1 (test for excess errors)
> FAIL: g++.dg/torture/pr59265.C -O2 (test for excess errors)
> FAIL: g++.dg/torture/pr59265.C -O2 -flto -fno-use-linker-plugin
> -flto-partition=none (test for excess errors)
> FAIL: g++.dg/torture/pr59265.C -O2 -flto -fuse-linker-plugin
> -fno-fat-lto-objects (test for excess errors)
> FAIL: g++.dg/torture/pr59265.C -O3 -g (test for excess errors)
> FAIL: g++.dg/torture/pr59265.C -Os (test for excess errors)
> FAIL: g++.dg/tree-prof/morefunc.C compilation, -fprofile-use -D_PROFILE_USE
> UNRESOLVED: g++.dg/tree-prof/morefunc.C execution, -fprofile-use
> -D_PROFILE_USE
>
> and more. Please get up to speed with GCC development and testing requirements!
>
> Richard.
I'll cook patch for it in order to remove the failures as soon as possible.
Martin
>
>> Thanks
>>
>>
>> On 09/24/2018 09:37 AM, Martin Sebor wrote:
>>> I would suggest to use the term "remove" or "delete" instead of
>>> the informal "wipe out" when referring to removing files or their
>>> contents.
>>>
>>> Martin
>>
next prev parent reply other threads:[~2018-09-27 10:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 19:29 Indu Bhagat
2018-09-11 9:21 ` Martin Liška
2018-09-16 8:28 ` Indu Bhagat
[not found] ` <159a29c5-8f8b-4194-dbea-1c9bd414db3a@oracle.com>
2018-09-17 10:10 ` Martin Liška
2018-09-17 11:20 ` Jan Hubicka
2018-09-18 19:41 ` Indu Bhagat
2018-09-21 23:23 ` Indu Bhagat
2018-09-24 16:46 ` Martin Sebor
2018-09-24 19:16 ` Indu Bhagat
2018-09-26 9:23 ` Martin Liška
2018-09-27 10:02 ` Richard Biener
2018-09-27 10:15 ` Martin Liška [this message]
2018-09-27 13:13 ` Martin Liška
2018-09-27 14:58 ` Richard Biener
2018-12-05 11:33 ` Thomas Schwinge
2018-12-07 1:46 ` Indu Bhagat
2018-12-10 20:45 ` Indu Bhagat
2018-12-11 9:14 ` Thomas Schwinge
2018-12-04 15:33 ` [committed, testsuite] Fix PR88310 Iain Sandoe
2018-09-11 9:23 ` [PATCH] PR86957 Martin Liška
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=ad8f6aed-869b-1187-3da4-8dfe038beafb@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=indu.bhagat@oracle.com \
--cc=msebor@gmail.com \
--cc=richard.guenther@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).