public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <rdsandiford@googlemail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Mike Stump <mikestump@comcast.net>,
	 Kenneth Zadeck <zadeck@naturalbridge.com>,
	 gcc@gcc.gnu.org,  gcc-patches@gcc.gnu.org
Subject: Re: we are starting the wide int merge
Date: Sat, 17 May 2014 08:33:00 -0000	[thread overview]
Message-ID: <87a9agztw1.fsf@talisman.default> (raw)
In-Reply-To: <alpine.LSU.2.11.1405161854490.2259@tuna.site> (Gerald Pfeifer's	message of "Fri, 16 May 2014 18:56:23 +0200 (CEST)")

Gerald Pfeifer <gerald@pfeifer.com> writes:
> On Sat, 10 May 2014, Gerald Pfeifer wrote:
>> Since (at least) 16:40 UTC that day my i386-unknown-freebsd10.0 builds
>> fail as follows:
>> 
>>   Comparing stages 2 and 3
>>   warning: gcc/cc1obj-checksum.o differs
>>   warning: gcc/cc1-checksum.o differs
>>   warning: gcc/cc1plus-checksum.o differs
>>   Bootstrap comparison failure!
>>   gcc/fold-const.o differs
>>   gcc/simplify-rtx.o differs
>>   gcc/tree-ssa-ccp.o differs
>> 
>> (FreeBSD/i386 really builds for i486, but retains the original name;
>> I'm traveling with limited access, but would not be surprised for this
>> to also show up for i386-*-linux-gnu or i486-*-linux-gnu.)
>
> Is anybody able to reproduce this, for example on a GNU/Linux system?
>
> This tester of mine hasn't been able to bootstrap for nearly a week,
> and timing-wise it would be really a coincidence were this not due to
> wide-int.

i386-linux-gnu won't bootstrap for me because there are no out-of-line
definitions of the sync_* routines.  I think this is expected.
i486-linux-gnu seems to bootstrap fine.

To rule out one possibility: which GCC are you using for stage1?

Thanks,
Richard

  reply	other threads:[~2014-05-17  8:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 15:19 Kenneth Zadeck
2014-05-06 19:21 ` Mike Stump
2014-05-06 21:17   ` Jan-Benedict Glaw
2014-05-06 22:54     ` Mike Stump
2014-05-06 23:03       ` Jan-Benedict Glaw
2014-05-06 23:16       ` Mike Stump
2014-05-06 23:53       ` Mike Stump
2014-05-06 22:59     ` Christophe Lyon
2014-05-07  7:48       ` Andreas Schwab
2014-05-07  9:40         ` Christophe Lyon
2014-05-07  7:07   ` Jan-Benedict Glaw
2014-05-07 10:27     ` Richard Sandiford
2014-05-08 22:48   ` iq2000-elf: wide-int fallout (was: we are starting the wide int merge) Jan-Benedict Glaw
2014-05-08 23:02     ` Oleg Endo
2014-05-08 23:06     ` UTItype fallout (was: wide-int fallout) Jan-Benedict Glaw
2014-05-10 19:42   ` we are starting the wide int merge Gerald Pfeifer
2014-05-16 16:56     ` Gerald Pfeifer
2014-05-17  8:33       ` Richard Sandiford [this message]
2014-05-19  3:08         ` Gerald Pfeifer
2014-05-19  6:47           ` Richard Sandiford
2014-05-19 17:33             ` Richard Sandiford

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=87a9agztw1.fsf@talisman.default \
    --to=rdsandiford@googlemail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=mikestump@comcast.net \
    --cc=zadeck@naturalbridge.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).