public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/37658] [4.3 Regression] long compile times in PRE on source with lots of labels/gotos Date: Wed, 01 Oct 2008 21:34:00 -0000 [thread overview] Message-ID: <20081001213239.24564.qmail@sourceware.org> (raw) In-Reply-To: <bug-37658-15165@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from rguenth at gcc dot gnu dot org 2008-10-01 21:32 ------- Confirmed. SCC consists of: MPT.765_6816(ab) ...[5000 others snipped]... code_6815 MPT.765_6793 Danny has some speedup ideas, apart from that you can tune --parm sccvn-max-scc-size. A value of 5000 shrinks compile-time to 2.4s. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dberlin at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37658
next prev parent reply other threads:[~2008-10-01 21:34 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-09-27 16:21 [Bug tree-optimization/37658] New: gcc-4.3 regression: long compile times " edwintorok at gmail dot com 2008-09-27 16:22 ` [Bug tree-optimization/37658] " edwintorok at gmail dot com 2008-09-28 19:38 ` [Bug tree-optimization/37658] [4.3 Regression] " pinskia at gcc dot gnu dot org 2008-09-28 19:43 ` [Bug tree-optimization/37658] [4.3 Regression] long compile times in PRE " pinskia at gcc dot gnu dot org 2008-10-01 21:34 ` rguenth at gcc dot gnu dot org [this message] 2008-10-10 9:16 ` rguenth at gcc dot gnu dot org 2009-01-24 10:26 ` rguenth at gcc dot gnu dot org 2009-08-04 12:43 ` rguenth at gcc dot gnu dot org 2010-05-22 18:31 ` rguenth at gcc dot gnu dot org [not found] <bug-37658-4@http.gcc.gnu.org/bugzilla/> 2011-06-27 11:47 ` rguenth at gcc dot gnu.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=20081001213239.24564.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).