From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: dclarke@blastwave.org
Cc: gcc Maillist <gcc@gcc.gnu.org>
Subject: Re: 4.5.2 20101213 (prerelease) ??
Date: Mon, 13 Dec 2010 16:19:00 -0000 [thread overview]
Message-ID: <AANLkTimuTeVXjRK7YfFPWXiCOX2ndnEXEqax8hDQjB8U@mail.gmail.com> (raw)
In-Reply-To: <43904.10.0.66.17.1292254314.squirrel@interact.purplecow.org>
On 13 December 2010 15:31, Dennis Clarke <dclarke@blastwave.org> wrote:
> Dear GCC folks :
>
> I have been closely watching the testsuite results as they come in and I
> have yet to see anyone do anything with the 4.5.2 RC for Solaris. Other
> than me of course. I have seen some work by Laurent GUERBY on 4.5.2 RC
> 20101213 ( on Linux ) which is NOT what I see at
> ftp://gcc.gnu.org/pub/gcc/snapshots/LATEST-4.5/
>
> So how does an outside community style hard working guy like me get the
> absolute latest ? Subversion only ? I'm just trying to do tests before the
> actual release and thus far I am seeing wonderful results :
>
> http://gcc.gnu.org/ml/gcc-testresults/2010-12/msg01062.html
>
> http://gcc.gnu.org/ml/gcc-testresults/2010-12/msg01063.html
>
> If there is some other snapshot or RC that I should be testing please let
> me know. Thank you dear GCC folks.
You get the latest gcc-4_5-branch (as always) from Subversion, but as
the branch is frozen you shouldn't need to. The only change I see
since the RC (rev 167585) is the daily bump to update the date in the
version string:
http://gcc.gnu.org/viewcvs/branches/gcc-4_5-branch/?sortby=rev&sortdir=down#dirlist
> --
> Dennis Clarke
> dclarke@opensolaris.ca <- Email related to the open source Solaris
> dclarke@blastwave.org <- Email related to open source for Solaris
>
>
>
>
>
>
next prev parent reply other threads:[~2010-12-13 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 15:32 Dennis Clarke
2010-12-13 16:19 ` Jonathan Wakely [this message]
2010-12-13 16:31 Dennis Clarke
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=AANLkTimuTeVXjRK7YfFPWXiCOX2ndnEXEqax8hDQjB8U@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=dclarke@blastwave.org \
--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).