public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dennis Clarke" <dclarke@blastwave.org>
To: "Richard Guenther" <richard.guenther@gmail.com>
Cc: "Andrew MacLeod" <amacleod@redhat.com>,  "GCC" <gcc@gcc.gnu.org>,
	 "Mark Mitchell" <mark@codesourcery.com>
Subject: Re: GCC 4.3 release schedule
Date: Fri, 26 Oct 2007 16:04:00 -0000	[thread overview]
Message-ID: <1485.72.39.216.186.1193414630.squirrel@mail.blastwave.org> (raw)
In-Reply-To: <84fc9c000710260851j28595611qb0413edcdea974be@mail.gmail.com>


> On 10/26/07, Andrew MacLeod <amacleod@redhat.com> wrote:
>> Richard Guenther wrote:
>> > On 10/26/07, Andrew MacLeod <amacleod@redhat.com> wrote:
>> >>

>
> ... when we think it's ready.  It doesn't help anyone to declare victory
> and release 4.3.0 when it still miscompiles the kernel (not that I know
> if it does).  Warm fuzzyness for PMs put aside.

At the risk of annoying you Red Hat Linux guys ( and Linux people in general
) you may be surprised to hear that there are problems for UNIX(tm) users
out there.  Now I have tried and failed to get a successful bootstrap build
of GCC 4.2.2 on Solaris 8 ( Sparc or x86 ) and on Solaris 10. When I look at
the Build status page I see no one has posted a result there for GCC 4.2.2 :

  Please see : http://gcc.gnu.org/gcc-4.2/buildstat.html

I was able to get a decent build with GCC 4.2.1 however :

     And see : http://gcc.gnu.org/ml/gcc-testresults/2007-08/msg00318.html

Exact same machine with exact same environment can not build GCC 4.2.2.

Now then, you seem to be discussing GCC 4.3 when GCC 4.2.x still does not
build correctly on a highly standards compliant UNIX platform.  Am I reading
this correctly ?  If not .. then please educate me if you can. I would like
to at least see GCC 4.2.2 bootstrap out of the box before flailing forwards
to GCC 4.3.x.

-
Dennis Clarke

  reply	other threads:[~2007-10-26 16:04 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 13:21 Andrew MacLeod
2007-10-26 14:05 ` Richard Guenther
2007-10-26 14:40   ` Andrew MacLeod
2007-10-26 15:54     ` Richard Guenther
2007-10-26 16:04       ` Dennis Clarke [this message]
2007-10-26 16:11         ` Richard Guenther
2007-10-26 16:32           ` Dennis Clarke
2007-10-26 18:06         ` Eric Botcazou
2007-10-26 18:14           ` Dennis Clarke
2007-10-26 18:20             ` Eric Botcazou
2007-10-26 18:41               ` Dennis Clarke
2007-10-26 21:02           ` Janis Johnson
2007-10-26 21:10             ` Eric Botcazou
2007-10-26 18:28       ` Martin Michlmayr
2007-10-26 19:03         ` Joe Buck
2007-10-26 20:49           ` Martin Michlmayr
2007-10-26 22:06             ` Joe Buck
2007-10-27  7:45               ` Martin Michlmayr
2007-10-31 19:10       ` Matthias Klose
2007-10-26 16:08     ` Mark Mitchell
2007-10-26 16:21       ` David Daney
2007-10-26 16:45         ` Dennis Clarke
2007-10-28 16:34           ` Jason Merrill
2007-10-26 16:21       ` Richard Guenther
2007-10-26 21:07       ` Andrew MacLeod
2007-11-01 16:50 ` Andrew Pinski
2007-11-01 17:38   ` Andrew MacLeod
2007-11-01 17:55   ` Jack Lloyd
2007-11-01 18:00     ` Daniel Jacobowitz
2007-11-01 18:27       ` Richard Guenther
2007-11-01 20:55         ` Gerald Pfeifer
2007-11-01 18:37     ` Andrew MacLeod
2007-10-29 15:24 Benjamin Kosnik
2007-10-29 15:54 ` Andrew MacLeod
2007-10-29 16:07   ` Benjamin Kosnik
2007-10-29 16:20     ` Richard Guenther
2007-10-29 18:04   ` Jason Merrill
2007-10-29 18:14     ` Andrew MacLeod
2007-10-29 18:29       ` Richard Guenther
2007-10-29 18:57         ` Andrew MacLeod
2007-10-29 19:37           ` Richard Guenther
2007-10-29 21:20           ` Eric Weddington
2007-10-29 22:18     ` Benjamin Kosnik
2007-10-29 22:43       ` Richard Guenther
2007-10-30  6:34         ` Mark Mitchell
2007-10-30 14:50       ` Jason Merrill
2007-10-30 15:18         ` Mark Mitchell
2007-11-01 15:45     ` Gerald Pfeifer
2007-11-01 16:01       ` Andrew MacLeod
2007-11-01 16:31         ` Benjamin Kosnik
2007-11-01 18:25           ` Richard Guenther
2007-11-01 21:39       ` Diego Novillo
2007-10-29 23:10 J.C. Pizarro

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=1485.72.39.216.186.1193414630.squirrel@mail.blastwave.org \
    --to=dclarke@blastwave.org \
    --cc=amacleod@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=richard.guenther@gmail.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).