From: Dennis Clarke <dclarke@blastwave.org>
To: Richard Guenther <rguenther@suse.de>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 4.5.1 Release Candidate available from gcc.gnu.org
Date: Fri, 23 Jul 2010 02:42:00 -0000 [thread overview]
Message-ID: <39434.10.0.66.17.1279852916.squirrel@interact.purplecow.org> (raw)
>
> A release canidate for GCC 4.5.1 is available from
>
> ftp://gcc.gnu.org/pub/gcc/snapshots/4.5.1-RC-20100722/
>
> and shortly its mirrors. It has been generated from SVN revision 162408.
>
> I have sofar bootstrapped and tested the release candidate on
> x86_64-unknown-linux-gnu. Please test it and report any issues to
> bugzilla.
>
> The branch remains frozen and all checkins until after the final
> release of GCC 4.5.1 require explicit RM approval.
>
> If all goes well, I'd like to release 4.5.1 before Aug 1st.
>
FYI , bug 44455 is a show stopper in the Solaris world.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44455
--
Dennis Clarke
dclarke@opensolaris.ca <- Email related to the open source Solaris
dclarke@blastwave.org <- Email related to open source for Solaris
next reply other threads:[~2010-07-23 2:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 2:42 Dennis Clarke [this message]
2010-07-23 8:17 ` Rainer Orth
-- strict thread matches above, loose matches on Subject: below --
2010-07-24 6:28 Dennis Clarke
2010-07-23 20:36 Dennis Clarke
2010-07-23 19:53 Dennis Clarke
2010-07-23 19:57 ` Eric Botcazou
2010-07-23 17:47 Dennis Clarke
2010-07-23 18:07 ` Toon Moene
2010-07-23 17:32 Dennis Clarke
2010-07-23 16:58 Dennis Clarke
2010-07-23 17:09 ` Andrew Pinski
2010-07-23 16:38 Dennis Clarke
2010-07-23 16:55 ` Andrew Pinski
2010-07-23 15:35 Dennis Clarke
2010-07-23 15:39 ` Richard Guenther
2010-07-23 17:43 ` Toon Moene
2010-07-23 19:06 ` Eric Botcazou
2010-07-22 11:06 Richard Guenther
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=39434.10.0.66.17.1279852916.squirrel@interact.purplecow.org \
--to=dclarke@blastwave.org \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).