From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org, gcc-announce@gcc.gnu.org
Subject: GCC 3.3: Second prerelease available
Date: Fri, 09 May 2003 16:48:00 -0000 [thread overview]
Message-ID: <1052498024.16075.71.camel@doubledemon.codesourcery.com> (raw)
The second GCC 3.3 prerelease is now available.
It is anticipated that these bits will become the final GCC 3.3 release
shortly.
Several problems found in the second prerelease have been fixed in this
prerelease, including a problem with exception-handling on S390, a
code-generation problem on SH processors, and a problem that prevented
building the Java library on some Solaris systems.
If you find problems in this prerelease, please do not send them
directly to me. Instead, put them in GNATS
http://gcc.gnu.org/cgi-bin/gnatsweb.pl
and list me on the "CC" line in the GNATS entry.
The prerelease itself is available at:
ftp://gcc.gnu.org/pub/gcc/snapshots
in the files that have "20030508" in their names.
Please do not send me requests to be unsubscribed from this mailing
list; I cannot process them. Visit:
http://gcc.gnu.org/lists.html
this page to unsubscribe.
Yours,
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
reply other threads:[~2003-05-09 16:48 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=1052498024.16075.71.camel@doubledemon.codesourcery.com \
--to=mark@codesourcery.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).