public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ianw at gelato dot unsw dot edu dot au" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/27414] IA64 bootstrap comparison failure, stage 2 -> 3
Date: Thu, 04 May 2006 23:43:00 -0000	[thread overview]
Message-ID: <20060504234346.22638.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27414-5429@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from ianw at gelato dot unsw dot edu dot au  2006-05-04 23:43 -------
The SVN version was

ianw@lime:/usr/src/gcc-svn$ svn info
Path: .
URL: svn://gcc.gnu.org/svn/gcc/trunk
Repository Root: svn://gcc.gnu.org/svn/gcc
Repository UUID: 138bc75d-0d04-0410-961f-82ee72b054a4
Revision: 113504
Node Kind: directory
Schedule: normal
Last Changed Author: kargl
Last Changed Rev: 113502
Last Changed Date: 2006-05-04 07:24:11 +1000 (Thu, 04 May 2006)
Properties Last Updated: 2006-01-31 08:52:35 +1100 (Tue, 31 Jan 2006)

Unlike PR20586 I didn't do anything tricky with flags, etc.

My understanding was the system gcc built stage 1, which then built 2 which
builds stage 3, so I would have thought the system gcc had less to do with a
stage 2 -> 3 problem, though I could be wildly off base.

I'm trying to re-build it now a few different ways, and I'll see what happens.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27414


  parent reply	other threads:[~2006-05-04 23:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04  6:49 [Bug c/27414] New: " ianw at gelato dot unsw dot edu dot au
2006-05-04  6:52 ` [Bug middle-end/27414] " pinskia at gcc dot gnu dot org
2006-05-04 16:05 ` sje at cup dot hp dot com
2006-05-04 16:19 ` pluto at agmk dot net
2006-05-04 23:43 ` ianw at gelato dot unsw dot edu dot au [this message]
2006-05-05  3:36 ` ianw at gelato dot unsw dot edu dot au

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=20060504234346.22638.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).