public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/43627] [4.5 Regression] slow compilation (tree canonical iv takes 75%) Date: Fri, 02 Apr 2010 14:17:00 -0000 [thread overview] Message-ID: <20100402141717.13661.qmail@sourceware.org> (raw) In-Reply-To: <bug-43627-6642@http.gcc.gnu.org/bugzilla/> ------- Comment #12 from jv244 at cam dot ac dot uk 2010-04-02 14:17 ------- (In reply to comment #9) > Created an attachment (id=20290) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20290&action=view) [edit] > smaller testcase (needs 3s, 80% in tree canonical iv) from valgrind, I see some 13000000 cals to get_val_for / fold_binary_loc, for the small testcase -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43627
next prev parent reply other threads:[~2010-04-02 14:17 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-02 8:14 [Bug tree-optimization/43627] New: [4.5 Regression] slow compilation jv244 at cam dot ac dot uk 2010-04-02 8:16 ` [Bug tree-optimization/43627] " jv244 at cam dot ac dot uk 2010-04-02 8:17 ` jv244 at cam dot ac dot uk 2010-04-02 8:28 ` [Bug tree-optimization/43627] [4.5 Regression] slow compilation (tree canonical iv ) jv244 at cam dot ac dot uk 2010-04-02 9:18 ` steven at gcc dot gnu dot org 2010-04-02 9:27 ` jv244 at cam dot ac dot uk 2010-04-02 9:47 ` jv244 at cam dot ac dot uk 2010-04-02 10:25 ` [Bug tree-optimization/43627] [4.5 Regression] slow compilation (tree canonical iv takes 75%) steven at gcc dot gnu dot org 2010-04-02 12:19 ` rguenth at gcc dot gnu dot org 2010-04-02 12:29 ` jv244 at cam dot ac dot uk 2010-04-02 14:07 ` rguenth at gcc dot gnu dot org 2010-04-02 14:07 ` jv244 at cam dot ac dot uk 2010-04-02 14:08 ` rguenth at gcc dot gnu dot org 2010-04-02 14:13 ` rguenth at gcc dot gnu dot org 2010-04-02 14:17 ` jv244 at cam dot ac dot uk [this message] 2010-04-02 14:23 ` rguenth at gcc dot gnu dot org 2010-04-02 14:27 ` rguenth at gcc dot gnu dot org 2010-04-02 14:39 ` rguenth at gcc dot gnu dot org 2010-04-02 14:53 ` rguenth at gcc dot gnu dot org 2010-04-02 15:10 ` rguenth at gcc dot gnu dot org 2010-04-03 17:17 ` rguenth at gcc dot gnu dot org 2010-04-06 11:28 ` rguenth at gcc dot gnu dot org 2010-04-06 12:33 ` rguenth at gcc dot gnu dot org 2010-04-06 12:33 ` rguenth at gcc dot gnu dot org 2010-04-15 13:47 ` rguenth at gcc dot gnu dot org 2010-04-15 13:47 ` 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=20100402141717.13661.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).