From: Richard Sandiford <rdsandiford@googlemail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Steven Bosscher <stevenb.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Vladimir Makarov <vmakarov@redhat.com>
Subject: Re: RFA: Fix debug-insn sensitivity in RA
Date: Sat, 07 Sep 2013 13:01:00 -0000 [thread overview]
Message-ID: <87ob84j17d.fsf@talisman.default> (raw)
In-Reply-To: <20130907114240.GW23437@tucnak.redhat.com> (Jakub Jelinek's message of "Sat, 7 Sep 2013 13:42:40 +0200")
Jakub Jelinek <jakub@redhat.com> writes:
> On Sat, Sep 07, 2013 at 12:37:14PM +0100, Richard Sandiford wrote:
>> Steven Bosscher <stevenb.gcc@gmail.com> writes:
>> > Can you please add a test case?
>>
>> What kind of test would you suggest? Do we have a harness for testing
>> that -O2 and -O2 -g .text output is identical?
>
> No, but we have -fcompare-debug, which is even stronger than that (compares
> final RTL, so can catch even differences that aren't visible in the .s file,
> but still are relevant). And, the default way of bootstrapping also
> compares .text etc. after stripping, between stage2 (built without debug)
> and stage3 (with debug).
Right, the bootstrap thing is what forced me to write the patch in
the first place. I probably wasn't clear, sorry, but the original
problem was a bootstrap comparison failure between stage 2 and stage 3
because the tree.o code depended on whether debug info was enabled.
I'll try to use -fcompare-debug though, thanks.
Richard
next prev parent reply other threads:[~2013-09-07 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 9:26 Richard Sandiford
2013-09-07 11:37 ` Steven Bosscher
2013-09-07 11:39 ` Richard Sandiford
2013-09-07 11:42 ` Steven Bosscher
2013-09-07 11:44 ` Jakub Jelinek
2013-09-07 13:01 ` Richard Sandiford [this message]
2013-09-07 16:42 ` Richard Sandiford
2013-09-08 15:57 ` Vladimir Makarov
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=87ob84j17d.fsf@talisman.default \
--to=rdsandiford@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=stevenb.gcc@gmail.com \
--cc=vmakarov@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).