From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
To: gcc-announce@gcc.gnu.org
Subject: GCC 4.1.1 Released
Date: Fri, 26 May 2006 05:22:00 -0000 [thread overview]
Message-ID: <200605260522.k4Q5M83Z006265@sethra.codesourcery.com> (raw)
GCC 4.1.1 has been released.
This release is a bug-fix release for problems in GCC 4.0.2. GCC
4.1.1 contains changes to correct regressions from previous releases,
but no new features.
This release is available from the FTP servers listed here:
http://www.gnu.org/order/ftp.html
The release is in the gcc/gcc-4.1.1 subdirectory.
If you encounter any difficulties using GCC 4.1.1, please do not send
them directly to me. Instead, please http://gcc.gnu.org/ for
information about getting help and filing problem reports.
As usual, a vast number of people contributed to this release -- far
too many to thank by name!
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713
reply other threads:[~2006-05-26 5:22 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=200605260522.k4Q5M83Z006265@sethra.codesourcery.com \
--to=mark@codesourcery.com \
--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).