public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/14179] [3.3/3.4/4.0 Regression] out of memory Date: Wed, 22 Sep 2004 15:54:00 -0000 [thread overview] Message-ID: <20040922155415.26953.qmail@sourceware.org> (raw) In-Reply-To: <20040217171044.14179.debora.j.estey@lmco.com> ------- Additional Comments From mark at codesourcery dot com 2004-09-22 15:54 ------- Subject: Re: [3.3/3.4/4.0 Regression] out of memory paolo dot bonzini at polimi dot it wrote: > and the operator-precedence was placed on the >wiki a week ago as a generic "speedup area", not a project that is >actively worked on unlike Matt's lexer overhaul: > > Honestly, we didn't know we'd be working on until the early part of this week. We didn't decided until Monday around noon in California. But, the fundamental point is that it's in nobody's best interest to duplicate work, so we will try to make as much noise as possible about projects. >http://www.dberlin.org/gccwiki/index.php/Speedup%20areas > >Since that page also mentions Nathan's "Add contains-repeated-base and >is diamond-shaped flags to classes" project, maybe it is *that* page >that needs to be louder. > > Just for the record, I do not know if Nathan is presently working on that or not. I think he may have concluded there is not enough win there. > > We'll try to be louder. > >No problem. You're doing a good work. > > Thanks for your understanding -- and you, likewise, are doing good work! After you get timing numbers for 14179, it would be interesting to consider whether or not we should try to extend the operator-precedence parser, or do other short-circuiting tricks, when getting down to the bottom of binary expressions. For example, if a unary expression is an integer literal or identifier followed by ")" or "," or ";" we know that it's just a primary expression. In other words, we could use two tokens of lookahead to zip straight to cp_parser_primary_expression. Would you like to take a look at that as well? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14179
next prev parent reply other threads:[~2004-09-22 15:54 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-17 17:10 [Bug c++/14179] New: " debora dot j dot estey at lmco dot com 2004-02-17 17:15 ` [Bug c++/14179] " debora dot j dot estey at lmco dot com 2004-02-17 17:25 ` debora dot j dot estey at lmco dot com 2004-02-17 17:52 ` giovannibajo at libero dot it 2004-02-17 18:00 ` [Bug c++/14179] [3.3/3.4/3.5 Regression] " pinskia at gcc dot gnu dot org 2004-02-17 18:10 ` pinskia at gcc dot gnu dot org 2004-03-08 23:08 ` mmitchel at gcc dot gnu dot org 2004-06-07 3:25 ` pinskia at gcc dot gnu dot org 2004-09-15 14:27 ` [Bug c++/14179] [3.3/3.4/4.0 " giovannibajo at libero dot it 2004-09-15 16:30 ` mark at codesourcery dot com 2004-09-17 18:50 ` giovannibajo at libero dot it 2004-09-18 13:10 ` giovannibajo at libero dot it 2004-09-20 23:05 ` cvs-commit at gcc dot gnu dot org 2004-09-21 21:12 ` cvs-commit at gcc dot gnu dot org 2004-09-21 22:50 ` cvs-commit at gcc dot gnu dot org 2004-09-21 23:46 ` cvs-commit at gcc dot gnu dot org 2004-09-22 0:36 ` giovannibajo at libero dot it 2004-09-22 0:38 ` giovannibajo at libero dot it 2004-09-22 0:43 ` giovannibajo at libero dot it 2004-09-22 0:54 ` mark at codesourcery dot com 2004-09-22 13:51 ` bonzini at gnu dot org 2004-09-22 15:33 ` mark at codesourcery dot com 2004-09-22 15:39 ` mmitchel at gcc dot gnu dot org 2004-09-22 15:43 ` paolo dot bonzini at polimi dot it 2004-09-22 15:54 ` mark at codesourcery dot com [this message] 2004-09-22 15:56 ` paolo dot bonzini at polimi dot it 2004-09-23 0:02 ` giovannibajo at libero dot it 2004-09-23 0:16 ` mark at codesourcery dot com 2004-09-23 1:00 ` giovannibajo at libero dot it 2004-09-23 1:37 ` mark at codesourcery dot com 2004-09-24 16:02 ` bonzini at gcc dot gnu dot org 2004-09-24 16:06 ` bonzini at gcc dot gnu dot org 2004-09-24 16:53 ` mark at codesourcery dot com 2004-09-24 18:53 ` bonzini at gnu dot org 2004-09-24 18:54 ` [Bug c++/14179] array parsing could be made faster bonzini at gcc dot gnu dot org 2004-09-25 0:50 ` [Bug c++/14179] [3.3/3.4/4.0 Regression] " giovannibajo at libero dot it 2004-10-26 16:11 ` [Bug c++/14179] [3.3/3.4/4.0 Regression] out of memory while parsing array with many initializers debora dot j dot estey at lmco dot com 2004-10-26 16:14 ` pinskia at gcc dot gnu dot org 2004-10-27 15:43 ` giovannibajo at libero dot it 2004-12-23 12:35 ` steven at gcc dot gnu dot org 2004-12-24 2:23 ` giovannibajo at libero dot it 2004-12-24 7:07 ` steven at gcc dot gnu dot org 2005-04-21 5:03 ` [Bug c++/14179] [3.3/3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org 2005-05-03 22:44 ` debora dot j dot estey at lmco dot com 2005-07-08 1:43 ` [Bug c++/14179] [3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org 2005-07-25 1:39 ` pinskia at gcc dot gnu dot org 2005-09-27 16:14 ` mmitchel at gcc dot gnu dot org
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=20040922155415.26953.qmail@sourceware.org \ --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: linkBe 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).