public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: GCC Release Status (2004-09-21)
Date: Wed, 22 Sep 2004 10:00:00 -0000	[thread overview]
Message-ID: <41510EA1.2090402@codesourcery.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 75 bytes --]


-- 
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com


[-- Attachment #2: gcc-status.txt --]
[-- Type: text/plain, Size: 1404 bytes --]

GCC 3.4.3
=========

There are 114 PRs targeted at 3.4.3.

Quite a number of these are usability nits: error messages that are
not ideal, misbehavior in the driver, etc.  Most of these have
work-arounds, but it would be nice if we could get some polish work
done on these issues. Most apply to 4.0 as well.  Examples include
PR17537, 17393, 17361, 13993, 15369.  

However, I still see nothing standing in the way of a November 1
release of GCC 3.4.3.

GCC 4.0
=======

There are 184 PRs targeted at 4.0, including those targeted at 3.4.3,
of which 32 are wrong-code bugs. I'm concerned about PR15014 (which
involves label differences), PR 15486 (-fdata-sections vs. common),
and PR 16721 (reads of volatile variables disappearing).

I'm glad to see Dan Berlin et. al. maintaining the Wiki page about
things in GCC 3.5.  I'm also glad to report that it looks like all of
the major 4.0 projects have now been submitted, as desired.  That's
great.  As of now, if it hasn't been submitted already, we're waiting
for 4.1.

Exactly when we'll create a release branch will depend on getting
these projects merged in, the Objective-C++ changes finished, and
getting some of the more important defects fixed.  I'd hope for some
time in October.

We do have some patches outstanding for review, and I hope that the
appropriate people will review some of those soon.

In the meantime, let's keep fixing those PRs!

             reply	other threads:[~2004-09-22  5:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 10:00 Mark Mitchell [this message]
2004-09-23 21:00 ` Joseph S. Myers
2004-09-23 22:41   ` Mark Mitchell
2004-09-24  2:46     ` Giovanni Bajo
2004-09-25  4:33       ` 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=41510EA1.2090402@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).