From: Mark Mitchell <mark@codesourcery.com>
To: gcc-announce@gcc.gnu.org, gcc@gcc.gnu.org
Subject: GCC 3.3 Prerelease
Date: Tue, 06 May 2003 16:25:00 -0000 [thread overview]
Message-ID: <1052237847.31850.96.camel@doubledemon.codesourcery.com> (raw)
The first GCC 3.3 prerelease is available on gcc.gnu.org:
ftp://gcc.gnu.org/pub/gcc/snapshots/gcc-*-3.3-20030506.tar.gz
The final GCC 3.3 release will contain very few changes, relative to
this code base, but it is likely that we will fix a few important bugs,
configuration problems, and/or packaging problems.
If you find problems in this pre-release, do not send them directly to
me. Instead, please file a bug-report here:
http://gcc.gnu.org/cgi-bin/gnatsweb.pl
and add my name to the CC list for the bug report.
If you do send me a report directly, I will simply return it to you with
a request to put it in GNATS, as above.
Yours,
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
next reply other threads:[~2003-05-06 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 16:25 Mark Mitchell [this message]
[not found] ` <20030506093345.A14675@synopsys.com>
2003-05-06 18:28 ` Mark Mitchell
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=1052237847.31850.96.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).