From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>, gcc@gcc.gnu.org
Subject: Re: combined enable-build-with-cxx bootstrap comparison failure
Date: Sat, 19 Sep 2009 09:12:00 -0000 [thread overview]
Message-ID: <4AB4A3D8.3020803@gmail.com> (raw)
In-Reply-To: <20090919074924.GA11080@gmx.de>
Ralf Wildenhues wrote:
> Comparing stages 2 and 3
> Bootstrap comparison failure!
> Now, what do I do to (help) debug this? Open a PR? Attach some of the
> object files (which)?
Well, ultimately, you could rebuild everything with --save-temps and take a
look at the .s files to see whether the difference in the .o files originates
there, or if it's purely a binutils problem - I'd imagine the former, and when
you see what the differences are you'll know where to look next.
> How do I know this is the same as (or different
> from) <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41340>?
That will probably not be apparent until both bugs are analyzed a bit more.
cheers,
DaveK
prev parent reply other threads:[~2009-09-19 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 7:49 Ralf Wildenhues
2009-09-19 9:12 ` Dave Korn [this message]
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=4AB4A3D8.3020803@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=gcc@gcc.gnu.org \
/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).