From: Gabriel Dos Reis <gdr@integrable-solutions.net>
To: Joe Buck <Joe.Buck@synopsys.COM>
Cc: gcc@gcc.gnu.org, Matthias Klose <doko@debian.org>
Subject: Re: 3.3.4 status, and some questions
Date: Fri, 12 Mar 2004 06:58:00 -0000 [thread overview]
Message-ID: <m37jxqtvay.fsf@uniton.integrable-solutions.net> (raw)
In-Reply-To: <20040311155833.A3294@synopsys.com>
Joe Buck <Joe.Buck@synopsys.COM> writes:
| I took a look at bugzilla and a first snapshot of what the release notes
| would be like, if we released now, appear below.
|
| I have some questions:
|
| - I successfully built 3.3.3 on an ia64 GNU/Linux box and did not observe
| a bootstrap failure.
The same here. Here at the Parasol Labs, we use gcc-3.3.3 internally
(along with gcc-3.5.x).
| Was 13918 something that only a very few people observed, or was it common?
This is a non-blocking issue. See the excellent explanation by Jim
Wilson. This is not a PR that would block 3.3.4.
Do you think there is any real urgence to release GCC-3.3.4 before
end of May?
-- Gaby
next prev parent reply other threads:[~2004-03-12 6:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 23:58 Joe Buck
2004-03-12 2:49 ` Ian Lance Taylor
2004-03-12 6:42 ` Matthias Klose
2004-03-12 10:44 ` Philip Blundell
2004-03-12 12:08 ` Richard Earnshaw
2004-03-12 12:44 ` Philip Blundell
2004-03-12 17:18 ` Joe Buck
2004-03-12 17:23 ` Richard Earnshaw
2004-03-12 16:46 ` Joe Buck
2004-03-12 16:50 ` Phil Blundell
2004-03-12 17:12 ` Joe Buck
2004-03-12 13:21 ` Gerhard Tonn
2004-03-12 17:17 ` Phil Blundell
2004-03-12 6:58 ` Gabriel Dos Reis [this message]
2004-03-12 9:57 ` Andreas Schwab
2004-03-14 22:12 ` Hans-Peter Nilsson
2004-03-16 8:57 ` Jim Wilson
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=m37jxqtvay.fsf@uniton.integrable-solutions.net \
--to=gdr@integrable-solutions.net \
--cc=Joe.Buck@synopsys.COM \
--cc=doko@debian.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).