public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58575] gcc should compile firefox code faster.
Date: Wed, 02 Oct 2013 10:26:00 -0000	[thread overview]
Message-ID: <bug-58575-4-Ca1uyUjtpW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58575-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58575

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manu at gcc dot gnu.org

--- Comment #2 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
That GCC could be much faster is well-known but how to make it so is less clear
and there is simply not enough people to do the work required. Currently there
is as many people working just on Clang than on the whole GCC (including all
languages, middle-end and backends).

Dimitrios Apostolou did some nice work on benchmarking, but his actual patches
did not bring impressive improvements:

http://gcc.gnu.org/wiki/OptimisingGCC

I don't know how much of this work ended up in GCC (if any).

There are many ideas on what could speed-up C++ parsing:

http://gcc.gnu.org/wiki/Speedup_areas#C.2B-.2B-_improvements

BTW, reducing memory allocation (or using smarter data structures) is likely to
bring significant improvements:

http://gcc.gnu.org/wiki/Speedup_areas#Some_general_thoughts_on_memory_usage

But at the end, someone needs to come up with very detailed benchmark data to
identify the real compile-time hogs and patches to address them.
>From gcc-bugs-return-430956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Oct 02 10:44:28 2013
Return-Path: <gcc-bugs-return-430956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 736 invoked by alias); 2 Oct 2013 10:44:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 687 invoked by uid 55); 2 Oct 2013 10:44:26 -0000
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58565] [c++11] ICE with label in statement expression
Date: Wed, 02 Oct 2013 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: paolo.carlini at oracle dot com
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58565-4-8kRoLRqq6f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58565-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58565-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2013-10/txt/msg00100.txt.bz2
Content-length: 683

http://gcc.gnu.org/bugzilla/show_bug.cgi?idX565

--- Comment #3 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> ---
Author: paolo
Date: Wed Oct  2 10:44:23 2013
New Revision: 203109

URL: http://gcc.gnu.org/viewcvs?rev 3109&root=gcc&view=rev
Log:
/cp
2013-10-02  Paolo Carlini  <paolo.carlini@oracle.com>

    PR c++/58565
    * semantics.c (potential_constant_expression_1): Handle LABEL_EXPR.

/testsuite
2013-10-02  Paolo Carlini  <paolo.carlini@oracle.com>

    PR c++/58565
    * g++.dg/parse/crash64.C: New.

Added:
    trunk/gcc/testsuite/g++.dg/parse/crash64.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/semantics.c
    trunk/gcc/testsuite/ChangeLog


      parent reply	other threads:[~2013-10-02 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-29 21:19 [Bug c++/58575] New: " tsaunders at mozilla dot com
2013-10-02  8:31 ` [Bug c++/58575] " paolo.carlini at oracle dot com
2013-10-02 10:26 ` manu at gcc dot gnu.org [this message]

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=bug-58575-4-Ca1uyUjtpW@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).