public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7086: [3.3/3.4 regression] compile time regression Date: Tue, 11 Mar 2003 02:36:00 -0000 [thread overview] Message-ID: <20030311023601.15387.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7086; it has been noted by GNATS. From: Daniel Jacobowitz <drow@mvista.com> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, brd@paradise.net.nz Cc: Subject: Re: c++/7086: [3.3/3.4 regression] compile time regression Date: Mon, 10 Mar 2003 21:32:25 -0500 Just FYI, I tried this with -O2 on: g++ (GCC) 3.3 20030129 (prerelease) The -ftime-report output was: Execution times (seconds) garbage collection : 1.56 ( 2%) usr 0.03 ( 3%) sys 3.00 ( 3%) wall cfg construction : 0.33 ( 0%) usr 0.02 ( 2%) sys 0.00 ( 0%) wall cfg cleanup : 1.38 ( 1%) usr 0.00 ( 0%) sys 1.00 ( 1%) wall trivially dead code : 0.30 ( 0%) usr 0.00 ( 0%) sys 1.00 ( 1%) wall life analysis : 0.33 ( 0%) usr 0.05 ( 5%) sys 0.00 ( 0%) wall life info update : 0.13 ( 0%) usr 0.01 ( 1%) sys 0.00 ( 0%) wall preprocessing : 0.13 ( 0%) usr 0.01 ( 1%) sys 0.00 ( 0%) wall lexical analysis : 0.10 ( 0%) usr 0.05 ( 5%) sys 0.00 ( 0%) wall parser : 0.95 ( 1%) usr 0.07 ( 7%) sys 1.00 ( 1%) wall expand : 85.42 (88%) usr 0.24 (25%) sys 86.00 (88%) wall varconst : 0.02 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall integration : 0.11 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall jump : 0.92 ( 1%) usr 0.10 (10%) sys 1.00 ( 1%) wall CSE : 0.93 ( 1%) usr 0.01 ( 1%) sys 0.00 ( 0%) wall global CSE : 0.73 ( 1%) usr 0.05 ( 5%) sys 1.00 ( 1%) wall loop analysis : 0.86 ( 1%) usr 0.23 (24%) sys 2.00 ( 2%) wall CSE 2 : 0.33 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall branch prediction : 0.19 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall flow analysis : 0.06 ( 0%) usr 0.01 ( 1%) sys 0.00 ( 0%) wall combiner : 0.13 ( 0%) usr 0.01 ( 1%) sys 0.00 ( 0%) wall if-conversion : 0.03 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall regmove : 0.11 ( 0%) usr 0.01 ( 1%) sys 0.00 ( 0%) wall mode switching : 0.04 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall local alloc : 0.23 ( 0%) usr 0.03 ( 3%) sys 0.00 ( 0%) wall global alloc : 0.40 ( 0%) usr 0.00 ( 0%) sys 1.00 ( 1%) wall reload CSE regs : 0.30 ( 0%) usr 0.01 ( 1%) sys 0.00 ( 0%) wall flow 2 : 0.07 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall peephole 2 : 0.04 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall rename registers : 0.10 ( 0%) usr 0.01 ( 1%) sys 0.00 ( 0%) wall scheduling 2 : 0.19 ( 0%) usr 0.01 ( 1%) sys 0.00 ( 0%) wall shorten branches : 0.05 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall final : 0.06 ( 0%) usr 0.00 ( 0%) sys 0.00 ( 0%) wall rest of compilation : 0.55 ( 1%) usr 0.00 ( 0%) sys 1.00 ( 1%) wall TOTAL : 97.10 0.96 98.00 I couldn't try the testcase on HEAD because it includes preprocessed output from the STL; the new parser rejects lots of it, for already well-discussed reasons. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2003-03-11 2:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-11 2:36 Daniel Jacobowitz [this message] 2003-03-12 10:56 Steven Bosscher 2003-03-24 8:32 mmitchel
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=20030311023601.15387.qmail@sources.redhat.com \ --to=drow@mvista.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).