From: Jakub Jelinek <jakub@redhat.com>
To: gcc-announce@gcc.gnu.org, gcc@gcc.gnu.org
Subject: GCC 4.3.1 Released
Date: Mon, 09 Jun 2008 15:06:00 -0000 [thread overview]
Message-ID: <20080609074931.GI13386@devserv.devel.redhat.com> (raw)
GCC 4.3.1 has been released.
GCC 4.3.1 is a bug-fix release, containing fixes for regressions in GCC
4.3.0 relative to previous GCC releases.
See:
http://gcc.gnu.org/gcc-4.3/changes.html
and particularly
http://gcc.gnu.org/gcc-4.3/changes.html#4.3.1
for more information about changes in GCC 4.3.1.
This release is available from the FTP servers listed here:
http://www.gnu.org/order/ftp.html
The release is in gcc/gcc-4.3.1/ subdirectory.
As always, a vast number of people contributed to this GCC release -- far
too many to thank individually!
reply other threads:[~2008-06-09 15:06 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=20080609074931.GI13386@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-announce@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).