public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/11611] [tree-ssa] Bootstrap failure on sparc-linux-gnu
Date: Thu, 24 Jul 2003 10:29:00 -0000	[thread overview]
Message-ID: <20030724102920.19899.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030720223228.11611.jim@phython.shacknet.nu>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From steven at gcc dot gnu dot org  2003-07-24 10:29 -------
There has been a new merge from the trunk yesterday.  Can you try with updated
sources?
(Yeah I know we're asking a lot of you, but then, SPARC machines are not as
popular as they used to be... :)

If that does not work, have you tried bootstrapping the trunk?  You didn't tell
if that does work for you, and if it does not, then this doesn't have to be a
tree-ssa problem.

Thanks!


  parent reply	other threads:[~2003-07-24 10:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-20 22:32 [Bug bootstrap/11611] New: " gcc-bugzilla at gcc dot gnu dot org
2003-07-20 22:39 ` [Bug bootstrap/11611] " pinskia at physics dot uc dot edu
2003-07-21  1:59 ` jim at phython dot shacknet dot nu
2003-07-21  2:01 ` pinskia at physics dot uc dot edu
2003-07-24 10:29 ` steven at gcc dot gnu dot org [this message]
2003-07-25 18:15 ` jim at phython dot shacknet dot nu
2003-08-05 23:39 ` pinskia at physics dot uc dot edu
2003-08-13 12:39 ` jim at phython dot shacknet dot nu
2003-08-13 12:42 ` pinskia at gcc dot gnu dot org
2003-10-01  3:51 ` pinskia at gcc dot gnu dot org
2003-10-17 14:54 ` pinskia at gcc dot gnu dot org
2003-11-14  6:46 ` steven at gcc dot gnu dot org
2003-11-15 22:02 ` jim at phython dot shacknet dot nu

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=20030724102920.19899.qmail@sources.redhat.com \
    --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).