From: Uros Bizjak <ubizjak@gmail.com>
To: Bernd Schmidt <bschmidt@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jeff Law <law@redhat.com>
Subject: Re: Enabling -frename-registers?
Date: Mon, 02 May 2016 11:21:00 -0000 [thread overview]
Message-ID: <CAFULd4YTGP1-JRe+KAfV7n16dFpiv--yTwL_xUYX0Bd=4FyjKA@mail.gmail.com> (raw)
In-Reply-To: <572736E2.4040506@redhat.com>
On Mon, May 2, 2016 at 1:15 PM, Bernd Schmidt <bschmidt@redhat.com> wrote:
> On 05/02/2016 01:12 PM, Uros Bizjak wrote:
>
>>> On 04/17/2016 08:59 PM, Jeff Law wrote:
>>>
>>>> invoke.texi has an independent list (probably incomplete! ;( of all the
>>>> things that -O2 enables. Make sure to add -frename-registers to that
>>>> list and this is Ok for the trunk (gcc-7).
>>>
>>>
>>> This is what I committed.
>>
>>
>> The patch introduced bootstrap failure on alpha-linux-gnu.
>>
>> Non-bootstrapped build regresses:
>>
>> FAIL: gcc.dg/torture/pr69542.c -O2 (test for excess errors)
>> FAIL: gcc.dg/torture/pr69542.c -O2 -flto -fno-use-linker-plugin
>> -flto-partition=none (test for excess errors)
>> FAIL: gcc.dg/torture/pr69542.c -Os (test for excess errors)
>>
>> where all failures are -fcompare-debug failures.
>
>
> Is the bootstrap failure also of this nature, or do you suspect something
> else?
I'm analysing the dumps, but I strongly suspect that it is the same problem.
(Please also note that the compiler includes Eric's PR 70886 patch [1]).
[1] https://gcc.gnu.org/ml/gcc-patches/2016-05/msg00026.html
Uros.
next prev parent reply other threads:[~2016-05-02 11:21 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 11:12 Uros Bizjak
2016-05-02 11:15 ` Bernd Schmidt
2016-05-02 11:21 ` Uros Bizjak [this message]
2016-05-02 11:58 ` Uros Bizjak
2016-05-02 13:20 ` Bernd Schmidt
2016-05-03 5:30 ` Uros Bizjak
-- strict thread matches above, loose matches on Subject: below --
2016-05-04 15:20 Wilco Dijkstra
2016-05-04 19:06 ` Eric Botcazou
2016-05-04 22:55 ` Pat Haugen
2016-05-05 7:42 ` Ramana Radhakrishnan
2016-05-05 13:00 ` Wilco Dijkstra
2016-05-05 16:24 ` Mike Stump
2016-04-29 13:02 David Edelsohn
2016-04-29 13:33 ` Bernd Schmidt
2016-04-29 13:42 ` David Edelsohn
2016-04-29 13:44 ` Bernd Schmidt
2016-04-29 13:48 ` David Edelsohn
2016-04-29 14:21 ` Richard Biener
2016-04-30 7:57 ` Andreas Schwab
2016-05-03 21:26 ` David Edelsohn
2016-05-03 22:53 ` Bernd Schmidt
2016-05-03 23:09 ` David Edelsohn
2016-05-04 8:39 ` Richard Biener
2016-05-04 9:05 ` Alan Modra
2016-05-04 9:08 ` Bernd Schmidt
2016-05-04 9:38 ` Alan Modra
2016-05-04 10:03 ` Eric Botcazou
2016-05-04 10:11 ` Bernd Schmidt
2016-05-04 10:26 ` Eric Botcazou
2016-05-04 13:25 ` Ramana Radhakrishnan
2016-05-04 13:37 ` Bernd Schmidt
2016-05-04 13:39 ` Ramana Radhakrishnan
2016-05-04 12:54 ` David Edelsohn
2016-05-04 17:50 ` Segher Boessenkool
2016-04-30 2:14 ` Segher Boessenkool
2016-05-02 13:32 ` Jeff Law
2016-05-11 4:07 ` Jeff Law
[not found] <56AB9759.407@t-online.de>
2016-01-29 17:34 ` Bernd Schmidt
2016-01-29 18:50 ` Richard Biener
2016-04-17 21:24 ` Jeff Law
2016-04-26 12:44 ` Bernd Schmidt
2016-04-27 7:11 ` Eric Botcazou
2016-04-27 9:58 ` Bernd Schmidt
2016-04-27 10:36 ` Eric Botcazou
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='CAFULd4YTGP1-JRe+KAfV7n16dFpiv--yTwL_xUYX0Bd=4FyjKA@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).