From: Mark Mitchell <mark@codesourcery.com>
To: gcc mailing list <gcc@gcc.gnu.org>
Subject: GCC 4.0.1 Status
Date: Thu, 23 Jun 2005 14:08:00 -0000 [thread overview]
Message-ID: <42BAC270.4010307@codesourcery.com> (raw)
As of now, please consider the GCC 4.0 branch completely frozen for all
changes, including documentation, testsuite, etc.
However, I'm not entirely happy with the state of the compiler from the
point of view of doing a release.
There are several PRs for wrong-code in 4.0.1 that seem potentially as
serious as the KDE thing. In order from most serious to least:
* PR 22043, which involves a failure to initialize fields in automatic
structures. The patch has been applied to the 4.0 branch, but the
target milestone still says 4.0.1. Bugmasters, is that just a mistake?
* PR 22000, in which we throw away volatile reads. That's a serious
problem for embedded targets.
* PR 22051, which involves wrong-code generation for pointer comparisons
on one of our primary platforms.
* PR 21985, in which we are mis-folding expressions involving pointer
arithmetic.
I'll wander over to the summit, and see whose brains are available for
picking about these things.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
next reply other threads:[~2005-06-23 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 14:08 Mark Mitchell [this message]
2005-06-23 14:45 ` Andrew Pinski
2005-06-23 21:05 ` 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=42BAC270.4010307@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).