From: Jan Hubicka <hubicka@ucw.cz>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Status Report (2004-09-13)
Date: Tue, 14 Sep 2004 01:28:00 -0000 [thread overview]
Message-ID: <20040914003056.GS378@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <414627A4.4080109@codesourcery.com>
>
> --
> Mark Mitchell
> CodeSourcery, LLC
> (916) 791-8304
> mark@codesourcery.com
>
> GCC 3.4.3
> =========
>
> I plan to do a GCC 3.4.3 release on or about November 1st, as
> expected. We seem to be reaching a pretty stable state on the GCC
> 3.4.x branch, and we'll continue to apply conservative fixes for
> regressions there.
>
> GCC 4.0
> =======
>
> There are 142 bugs targeted at GCC 4.0 -- which is not too bad, and
> it's nice to see that RTH and others are swatting these bugs at a
> pretty rapid pace. I'm happy to see that only 32 of the bugs are
> optimization bugs; those are often the hardest to fix. Unfortunately,
> some significant fraction of the 107 bugs targeted at 3.4.3 are also
> GCC 4.0 bugs.
>
> =======
>
> Here is an update on the GCC projects for 4.0, as previously posted.
>
> What is the status of:
>
> * Tree-based branch prediction [Hubicka]
>
> September 5
>
> ?
>
> I lost track of this project.
The patches are ready and I've just sent two for integration (one you
responded to), other three (return value predictors, dom updating fixes
and the overall switch to tree predictors) are in testing and
benchmarking now. I understand that it is 14th intead of 5th, so if you
want to postnote the project, I won't complain strongly.
My understanding was that projects needs to be done till 29th so I
looked into some of bugfixes and compilation speed/memory issues in
meantime too (since the mainline got into somewhat unstable state) that
somewhat delayed me.
Honza
next prev parent reply other threads:[~2004-09-14 0:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 0:30 Mark Mitchell
2004-09-14 1:14 ` Andrew Pinski
2004-09-14 1:28 ` Jan Hubicka [this message]
2004-09-14 5:02 ` Jeffrey A Law
2004-09-14 5:58 ` Mark Mitchell
2004-09-14 6:29 ` Jeffrey A Law
2004-09-14 15:54 ` Jan Hubicka
2004-09-14 17:07 ` Mark Mitchell
2004-09-14 6:28 ` Mark Mitchell
2004-09-15 21:25 ` Scott Robert Ladd
2004-09-16 21:58 ` Mark Mitchell
2004-09-16 15:58 ` GCC Status Report (2004-09-13) [--enable-mapped-location] Per Bothner
2004-09-16 18:45 ` Mark Mitchell
2004-09-16 18:56 ` Per Bothner
2004-09-16 19:02 ` Mark Mitchell
2004-09-16 19:03 ` Matt Austern
2004-09-16 19:31 ` Mark Mitchell
2004-09-16 22:50 ` Steven Bosscher
2004-09-16 19:28 ` Per Bothner
2004-09-16 19:46 ` Mark Mitchell
2004-09-14 4:48 GCC Status Report (2004-09-13) Wolfgang Bangerth
2004-09-18 11:02 Paolo Bonzini
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=20040914003056.GS378@atrey.karlin.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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).