From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21131 invoked by alias); 13 Sep 2004 23:05:16 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 21121 invoked from network); 13 Sep 2004 23:05:15 -0000 Received: from unknown (HELO mail.codesourcery.com) (65.74.133.10) by sourceware.org with SMTP; 13 Sep 2004 23:05:15 -0000 Received: (qmail 17066 invoked from network); 13 Sep 2004 23:05:14 -0000 Received: from localhost (HELO ?192.168.0.105?) (mitchell@127.0.0.1) by mail.codesourcery.com with SMTP; 13 Sep 2004 23:05:14 -0000 Message-ID: <414627A4.4080109@codesourcery.com> Date: Tue, 14 Sep 2004 00:30:00 -0000 From: Mark Mitchell Organization: CodeSourcery, LLC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616 MIME-Version: 1.0 To: gcc@gcc.gnu.org Subject: GCC Status Report (2004-09-13) Content-Type: multipart/mixed; boundary="------------020302040004040301090207" X-SW-Source: 2004-09/txt/msg00806.txt.bz2 This is a multi-part message in MIME format. --------------020302040004040301090207 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-length: 75 -- Mark Mitchell CodeSourcery, LLC (916) 791-8304 mark@codesourcery.com --------------020302040004040301090207 Content-Type: text/plain; name="gcc-status.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="gcc-status.txt" Content-length: 3734 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. Patches to implement these projects have been submitted: * Convert RTL passes to use pass manager [Nerode/Bonzini] * Edges-in-vectors conversion [Elliston] * Analysis of usage of compilation unit static variables and removal of spurious clobbering vdef based on the information [Zadeck] * Vectorize unknown-loop-bound support [Golovanevsky] * Linear loop transforms [Berlin] * Variable expansion optimization [Eres] * Tree-based profile-directed feedback [Hubicka] Some have been reviewed, some have not, but we seem to be making good progress on all of them. I'm very pleased to see the submitters working hard to hit these dates. These projects have missed the target dates, and will be postponed until GCC 4.1. (No criticism is implied; these just didn't get done.) September 5 * Immediate use integration [MacLeod] * Top-level bootstrap [Bonzini/Nerode] * Automatic dependency for GCC builds [Weinberg] These projects are still on the plan: September 19 * Fix/finish --enable-mapped-location [Bothner] * General compile-time performance improvements [Weinberg] (Although more may be acceptable later in Stage 3, as makes sense.) * Use the previous project to promote non-escaping static variables into true ssa variables [Zadeck] * Vectorizer peeling-for-alignment support [Golovanevsky] * Vectorizer additional data-references support [Rosen] * LNO branch merge [Dvorak] ======= Some people have expressed interest in knowing which PRs I see as particularly high priority. For now, I'm going to confine myself to wrong-code bugs -- of which there are 35. For now, I've confined myself to wrong-code regressions; here are some that concern me especially much: PR 16381 This is a structure layout issue, and therefore potentially ABI-breaking. It's a corner case, but I'm not sure how uncommon of a corner case. PR 17252 This is an aliasing problem that looks likely to affect a fair amount of code. Since it looks likes Diego's testing a patch, this will probably go away quickly. PR 17324 This is a C++ case that looks like we may be stomping memory, with who-knows-what unpredictable side-effects. PR 15846 This is -fdata-sections vs. common variables; I'd really like to get this resolved because it does seem to be confusing people. Jason is open to having a part of his patch reverted, but we need to get some testing cycles there. PR 17251 This is a problem with the ELF visibility attribute; we need to specify the behavior we want, and then, perhaps implement it. Best we do this before 4.0 gets out and we have compatibility problems. PR 15923 This is a testsuite regression on PowerPC, probably involving varargs in some way. There are also 40 ice-on-valid-code bugs, including several bootstrap failures. Those are pretty serious; in particular PR 17427, which is a bootstrap failure on PowerPC GNU/Linux is clearly a must-fix. --------------020302040004040301090207--