From: gccadmin@gcc.gnu.org
To: gcc@gcc.gnu.org
Subject: gcc-6-20170510 is now available
Date: Wed, 10 May 2017 22:37:00 -0000 [thread overview]
Message-ID: <20170510223704.23373.qmail@sourceware.org> (raw)
Snapshot gcc-6-20170510 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20170510/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6-branch revision 247868
You'll find:
gcc-6-20170510.tar.bz2 Complete GCC
SHA256=d758a3a63dd2553fe2bfda39afa21a2e119692b416418cb278f8f513fd407f12
SHA1=0291b35cd6a2767868595d4f02a9511c938883cb
Diffs from 6-20170503 are available in the diffs/ subdirectory.
When a particular snapshot is ready for public consumption the LATEST-6
link is updated and a message is sent to the gcc list. Please do not use
a snapshot before it has been announced that way.
reply other threads:[~2017-05-10 22:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170510223704.23373.qmail@sourceware.org \
--to=gccadmin@gcc.gnu.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).