public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
Cc: rearnshaw@arm.com, obrien@FreeBSD.org, geoffk@geoffk.org
Cc: dje@watson.ibm.com, rth@redhat.com, davem@redhat.com
Cc: jakub@redhat.com, joern.rennecke@superh.com, aoliva@redhat.com
Cc: per@bothner.com, apbianco@redhat.com, aph@redhat.com, jh@suse.cz
Subject: GCC 3.3 Status
Date: Tue, 22 Apr 2003 23:14:00 -0000	[thread overview]
Message-ID: <200304222140.h3MLe2YH010191@doubledemon.codesourcery.com> (raw)


If you are in the CC list for this email, please read this entire
message.

As of now, we've got 32 high-priority PRs against GCC 3.3.

I'm going to downgrade some of these, including doc issues,
"misleading" (but correct) error messages, etc.  In fact, if we do not
get closure quickly, it is my intention (assuming the SC does not
override my decision) to ship 3.3 with virtually *all* of these PRs
unfixed.  Very few open 3.3 PRs affect primary targets, and of those
that do, most are ice-on-illegal rather than wrong-code, and of those
that are wrong-code, nobody seems to be making any progress on fixing
them.

I intend to personally tackle most of the remaining C++ issues,
including trying to make a little more progress on the compile-time
issues with respect to inlining, probably by doing the appropriate
double-counting of CLEANUP_STMTs.

Below is a list of PRs that are apparently port-specific, together
with the maintainers for that port.  Maintainers, please let me know
that (a) you intend to tackle these PRs in the next few days (by
assigning them to yourself) or at least (b) that you are not going to
try to fix them, by sending mail to me.  Please do either (a) or (b)
so that I know what we have a chance to fix and what we do not.

If you choose (b), GCC 3.3 will probably ship without a fix for the
PR.

If you can, please spend a little time to fix up just one PR; if each
port maintainer below does that, we'll nail almost all of them.

It is my intention to make the first GCC 3.3 prerelease in the early
part of next week.  The branch will close to patches that do not have
my approval at that time.

Here is the list of open PRs:

Geoff Keating, David Edelsohn:

  PR 9745, 10315: PowerPC

Richard Earnshaw:

  PR 6860, PR 10206: ARM

David O'Brien, Richard Henderson, David Miller, Jakub Jelinek:

  PR 10453: SPARC/FreeBSD 

Richard Henderson, David Miller, Jakub Jelinek:

  PR 8300, PR 10160: SPARC

Jeff Law:

  PR 10021, PR 9812: m68k

Joern Rennecke, Alexandre Oliva:

  PR 9594: SH
  
Richard Henderson:

  PR 10308: x86

Per Bothner, Alexandre Petit-Biano, Andrew Haley:

  PR 10353: Java

Jan Hubicka:

  PR 9929: x86 assigned to you
  
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

             reply	other threads:[~2003-04-22 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 23:14 Mark Mitchell [this message]
2003-04-23 14:19 ` Jan Hubicka
2003-04-22 23:55 S. Bosscher
2003-04-28  8:14 ` Mark Mitchell
2005-04-20 10:56 GCC 3.3 status Giovanni Bajo
2005-04-20 15:21 ` Gabriel Dos Reis

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=200304222140.h3MLe2YH010191@doubledemon.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@geoffk.org \
    --cc=obrien@FreeBSD.org \
    --cc=rearnshaw@arm.com \
    /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).