public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kgardas at objectsecurity dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/13775] [3.4/3.5 Regression] Many C++ compile-time regression in 3.4.0 in comparison with 3.3.2
Date: Fri, 30 Jan 2004 21:15:00 -0000	[thread overview]
Message-ID: <20040130211504.17452.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040120183448.13775.kgardas@objectsecurity.com>


------- Additional Comments From kgardas at objectsecurity dot com  2004-01-30 21:14 -------
Subject: Re:  [3.4/3.5 Regression] Many C++ compile-time
 regression in 3.4.0 in comparison with 3.3.2


Sure! Here we go: (I've tested typecode.cc as it is the worst case)

thinkpad:/mnt/karel/mico/orb$ time make typecode.pic.o
c++  -I../include  -time -ftime-report -O2  -Wall   -DPIC -fPIC  -c typecode.cc -o typecode.pic.o

Execution times (seconds)
 garbage collection    :   2.41 ( 7%) usr   0.00 ( 0%) sys   2.45 ( 6%) wall
 callgraph construction:   0.14 ( 0%) usr   0.00 ( 0%) sys   0.14 ( 0%) wall
 callgraph optimization:   0.01 ( 0%) usr   0.00 ( 0%) sys   0.01 ( 0%) wall
 cfg construction      :   0.31 ( 1%) usr   0.02 ( 2%) sys   0.34 ( 1%) wall
 cfg cleanup           :   0.49 ( 1%) usr   0.01 ( 1%) sys   0.52 ( 1%) wall
 trivially dead code   :   0.52 ( 1%) usr   0.00 ( 0%) sys   0.52 ( 1%) wall
 life analysis         :   0.98 ( 3%) usr   0.00 ( 0%) sys   1.00 ( 3%) wall
 life info update      :   0.43 ( 1%) usr   0.00 ( 0%) sys   0.44 ( 1%) wall
 alias analysis        :   0.80 ( 2%) usr   0.02 ( 2%) sys   0.82 ( 2%) wall
 register scan         :   0.41 ( 1%) usr   0.00 ( 0%) sys   0.41 ( 1%) wall
 rebuild jump labels   :   0.20 ( 1%) usr   0.00 ( 0%) sys   0.20 ( 1%) wall
 preprocessing         :   0.38 ( 1%) usr   0.10 ( 8%) sys   0.51 ( 1%) wall
 parser                :   4.38 (12%) usr   0.34 (26%) sys   4.88 (13%) wall
 name lookup           :   2.32 ( 6%) usr   0.40 (30%) sys   2.88 ( 7%) wall
 expand                :   8.22 (23%) usr   0.00 ( 0%) sys   8.42 (22%) wall
 varconst              :   0.05 ( 0%) usr   0.02 ( 2%) sys   0.07 ( 0%) wall
 integration           :   1.50 ( 4%) usr   0.02 ( 2%) sys   1.73 ( 4%) wall
 jump                  :   0.62 ( 2%) usr   0.11 ( 8%) sys   0.77 ( 2%) wall
 CSE                   :   2.60 ( 7%) usr   0.00 ( 0%) sys   2.68 ( 7%) wall
 global CSE            :   2.46 ( 7%) usr   0.15 (11%) sys   2.67 ( 7%) wall
 loop analysis         :   0.13 ( 0%) usr   0.00 ( 0%) sys   0.14 ( 0%) wall
 bypass jumps          :   0.29 ( 1%) usr   0.03 ( 2%) sys   0.35 ( 1%) wall
 CSE 2                 :   0.82 ( 2%) usr   0.00 ( 0%) sys   0.84 ( 2%) wall
 branch prediction     :   0.40 ( 1%) usr   0.01 ( 1%) sys   0.41 ( 1%) wall
 flow analysis         :   0.04 ( 0%) usr   0.00 ( 0%) sys   0.04 ( 0%) wall
 combiner              :   0.48 ( 1%) usr   0.00 ( 0%) sys   0.50 ( 1%) wall
 if-conversion         :   0.08 ( 0%) usr   0.00 ( 0%) sys   0.08 ( 0%) wall
 regmove               :   0.19 ( 1%) usr   0.00 ( 0%) sys   0.19 ( 0%) wall
 local alloc           :   0.42 ( 1%) usr   0.02 ( 2%) sys   0.44 ( 1%) wall
 global alloc          :   1.12 ( 3%) usr   0.02 ( 2%) sys   1.19 ( 3%) wall
 reload CSE regs       :   0.48 ( 1%) usr   0.00 ( 0%) sys   0.48 ( 1%) wall
 flow 2                :   0.10 ( 0%) usr   0.00 ( 0%) sys   0.14 ( 0%) wall
 if-conversion 2       :   0.08 ( 0%) usr   0.00 ( 0%) sys   0.09 ( 0%) wall
 peephole 2            :   0.12 ( 0%) usr   0.00 ( 0%) sys   0.15 ( 0%) wall
 rename registers      :   0.13 ( 0%) usr   0.01 ( 1%) sys   0.15 ( 0%) wall
 scheduling 2          :   0.69 ( 2%) usr   0.01 ( 1%) sys   0.75 ( 2%) wall
 reorder blocks        :   0.07 ( 0%) usr   0.00 ( 0%) sys   0.07 ( 0%) wall
 shorten branches      :   0.10 ( 0%) usr   0.00 ( 0%) sys   0.10 ( 0%) wall
 final                 :   0.30 ( 1%) usr   0.00 ( 0%) sys   0.31 ( 1%) wall
 symout                :   0.01 ( 0%) usr   0.01 ( 1%) sys   0.02 ( 0%) wall
 rest of compilation   :   1.00 ( 3%) usr   0.01 ( 1%) sys   1.05 ( 3%) wall
 TOTAL                 :  36.31             1.32            38.99
# cc1plus 36.31 1.33
# as 0.29 0.02

real    0m40.410s
user    0m37.000s
sys     0m1.400s


Cheers,

Karel




-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13775


  parent reply	other threads:[~2004-01-30 21:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20 18:34 [Bug c++/13775] New: " kgardas at objectsecurity dot com
2004-01-20 18:52 ` [Bug c++/13775] " bangerth at dealii dot org
2004-01-20 18:53 ` bangerth at dealii dot org
2004-01-23 13:26 ` mattyt-bugzilla at tpg dot com dot au
2004-01-23 23:14 ` pinskia at gcc dot gnu dot org
2004-01-24  3:33 ` pinskia at gcc dot gnu dot org
2004-01-28 17:58 ` pinskia at gcc dot gnu dot org
2004-01-28 18:01 ` kgardas at objectsecurity dot com
2004-01-28 18:04 ` pinskia at gcc dot gnu dot org
2004-01-29 11:29 ` kgardas at objectsecurity dot com
2004-01-29 15:17 ` [Bug optimization/13775] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-01-30 19:25 ` bonzini at gnu dot org
2004-01-30 21:15 ` kgardas at objectsecurity dot com [this message]
2004-02-04 16:38 ` [Bug middle-end/13775] " pinskia at gcc dot gnu dot org
2004-02-05  4:56 ` roger at eyesopen dot com
2004-03-13 16:31 ` mmitchel 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=20040130211504.17452.qmail@sources.redhat.com \
    --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: link
Be 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).