public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/18687] [4.3/4.4/4.5 Regression] ~50% compile time regression Date: Mon, 28 Dec 2009 20:46:00 -0000 [thread overview] Message-ID: <20091228204609.14426.qmail@sourceware.org> (raw) In-Reply-To: <bug-18687-7958@http.gcc.gnu.org/bugzilla/> ------- Comment #49 from steven at gcc dot gnu dot org 2009-12-28 20:46 ------- For hashes100.c, combine+IRA+expand+tree-PRE accounts for 1/3 of the total compile time. For infcodes100.c, the profile is more flat, but IRA+expand still account for 1/4 of the total compile time. Why is IRA so slow? -- steven at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmakarov at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18687
next prev parent reply other threads:[~2009-12-28 20:46 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-18687-7958@http.gcc.gnu.org/bugzilla/> 2005-10-31 1:59 ` [Bug tree-optimization/18687] [4.0/4.1 " mmitchel at gcc dot gnu dot org 2006-02-24 0:31 ` [Bug tree-optimization/18687] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org 2006-05-25 2:32 ` mmitchel at gcc dot gnu dot org 2006-07-05 9:15 ` pinskia at gcc dot gnu dot org 2006-09-03 11:05 ` steven at gcc dot gnu dot org 2006-09-03 11:37 ` steven at gcc dot gnu dot org 2006-09-03 11:41 ` steven at gcc dot gnu dot org 2006-09-03 13:22 ` rguenth at gcc dot gnu dot org 2006-09-03 17:28 ` steven at gcc dot gnu dot org 2007-02-14 9:04 ` [Bug tree-optimization/18687] [4.0/4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org 2007-10-09 18:57 ` hubicka at gcc dot gnu dot org 2007-11-05 22:23 ` steven at gcc dot gnu dot org 2008-07-04 16:47 ` [Bug tree-optimization/18687] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2009-01-31 21:36 ` rguenth at gcc dot gnu dot org 2009-01-31 22:22 ` steven at gcc dot gnu dot org 2009-02-01 11:08 ` rguenth at gcc dot gnu dot org 2009-03-31 16:42 ` [Bug tree-optimization/18687] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org 2009-08-04 12:28 ` rguenth at gcc dot gnu dot org 2009-12-28 19:51 ` steven at gcc dot gnu dot org 2009-12-28 20:28 ` steven at gcc dot gnu dot org 2009-12-28 20:35 ` steven at gcc dot gnu dot org 2009-12-28 20:39 ` steven at gcc dot gnu dot org 2009-12-28 20:40 ` steven at gcc dot gnu dot org 2009-12-28 20:46 ` steven at gcc dot gnu dot org [this message] 2010-01-04 23:11 ` [Bug tree-optimization/18687] [4.3/4.4/4.5 Regression] >200% compile time regression compared to gcc-3.4 rguenth at gcc dot gnu dot org 2010-05-22 18:12 ` [Bug tree-optimization/18687] [4.3/4.4/4.5/4.6 " rguenth 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=20091228204609.14426.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).