From: Richard Biener <richard.guenther@gmail.com>
To: gcc@gcc.gnu.org,Jan Hubicka <hubicka@ucw.cz>,Jeff Law <law@redhat.com>
Cc: "Дмитрий Дьяченко" <dimhen@gmail.com>,
"Andreas Schwab" <schwab@suse.de>,
"Daniel Santos" <daniel.santos@pobox.com>, gcc <gcc@gcc.gnu.org>
Subject: Re: .bad_compare in bootstrap of head
Date: Fri, 05 May 2017 13:54:00 -0000 [thread overview]
Message-ID: <170B23E5-44FC-40DC-AA13-ED374BF2E84F@gmail.com> (raw)
In-Reply-To: <20170505130343.GA82320@kam.mff.cuni.cz>
On May 5, 2017 3:03:43 PM GMT+02:00, Jan Hubicka <hubicka@ucw.cz> wrote:
>> > I wonder how that patch can cause mismatches. Does it reproduce on
>one of
>> > compile farm machines (my x86-64 bootstrap works fine so does ia64
>on terbium
>> > after fixing the gcc 4.1 issue yeterday).
>> > It would be great to have -fdump-ipa-inline-details dumps of the
>mismatching
>> > run. Perhaps it will be easy to spot the problem.
>>
>> Aha, --enable-checking=no. I will check what effect it have.
>
>It does reproduce for me. Time estimates are very slightly different
>between
>checking and non-checking build. I am investigating why.
You mean debugging and non-debugging build?
Richard.
>Honza
>>
>> Honza
next prev parent reply other threads:[~2017-05-05 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 2:59 Daniel Santos
2017-05-04 6:59 ` Andreas Schwab
2017-05-04 13:05 ` Jeff Law
2017-05-04 13:27 ` Дмитрий Дьяченко
2017-05-04 14:31 ` Jeff Law
2017-05-04 17:49 ` Jeff Law
2017-05-05 10:37 ` Jan Hubicka
2017-05-05 10:40 ` Jan Hubicka
2017-05-05 13:03 ` Jan Hubicka
2017-05-05 13:54 ` Richard Biener [this message]
2017-05-05 23:13 ` Daniel Santos
2017-05-07 22:33 ` Jan Hubicka
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=170B23E5-44FC-40DC-AA13-ED374BF2E84F@gmail.com \
--to=richard.guenther@gmail.com \
--cc=daniel.santos@pobox.com \
--cc=dimhen@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=law@redhat.com \
--cc=schwab@suse.de \
/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).