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 debug/44694] [4.5/4.6 Regression] Long var tracking compile time of GiNaC tests Date: Mon, 28 Jun 2010 09:13:00 -0000 [thread overview] Message-ID: <20100628091308.15353.qmail@sourceware.org> (raw) In-Reply-To: <bug-44694-176@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2010-06-28 09:13 ------- Confirmed. At -O2 -g we get for 4.4.x variable tracking : 0.26 ( 1%) usr 0.00 ( 0%) sys 0.24 ( 1%) wall 1870 kB ( 1%) ggc TOTAL : 26.74 1.19 29.62 282737 kB while for the current 4.5 branch we have variable tracking : 392.60 (96%) usr 2.69 (73%) sys 397.72 (96%) wall 30099 kB (11%) ggc TOTAL : 409.66 3.69 415.97 279266 kB -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |compile-time-hog Last reconfirmed|0000-00-00 00:00:00 |2010-06-28 09:13:08 date| | Summary|[4.4 4.5 regression] Long |[4.5/4.6 Regression] Long |var tracking compile time of|var tracking compile time of |GiNaC tests |GiNaC tests Target Milestone|--- |4.5.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44694
next prev parent reply other threads:[~2010-06-28 9:13 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-27 23:56 [Bug debug/44694] New: [4.4 4.5 regression] " hubicka at gcc dot gnu dot org 2010-06-27 23:57 ` [Bug debug/44694] " hubicka at gcc dot gnu dot org 2010-06-28 9:13 ` rguenth at gcc dot gnu dot org [this message] 2010-06-28 9:14 ` [Bug debug/44694] [4.5/4.6 Regression] " rguenth at gcc dot gnu dot org 2010-06-28 16:13 ` jakub at gcc dot gnu dot org 2010-06-29 6:29 ` jakub at gcc dot gnu dot org 2010-06-29 8:53 ` jakub at gcc dot gnu dot org 2010-06-29 9:09 ` jakub at gcc dot gnu dot org 2010-06-29 14:12 ` jakub at gcc dot gnu dot org 2010-06-30 6:13 ` jakub at gcc dot gnu dot org 2010-06-30 7:16 ` [Bug debug/44694] [4.5 " jakub at gcc dot gnu dot org 2010-06-30 15:41 ` jakub at gcc dot gnu dot org 2010-06-30 23:42 ` rearnsha at gcc dot gnu dot org 2010-06-30 23:44 ` rearnsha at gcc dot gnu dot org 2010-06-30 23:55 ` rearnsha at gcc dot gnu dot org 2010-07-01 7:14 ` jakub at gcc dot gnu dot org 2010-07-01 7:24 ` jakub at gcc dot gnu dot org 2010-07-01 11:12 ` jakub at gcc dot gnu dot org 2010-07-01 11:13 ` jakub at gcc dot gnu dot org 2010-07-01 12:37 ` jakub 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=20100628091308.15353.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).