public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dnovillo at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13776] [tree-ssa] Many C++ compile-time regression in 3.5-tree-ssa 040120 Date: Wed, 03 Mar 2004 15:06:00 -0000 [thread overview] Message-ID: <20040303150639.27819.qmail@sources.redhat.com> (raw) In-Reply-To: <20040120183908.13776.kgardas@objectsecurity.com> ------- Additional Comments From dnovillo at redhat dot com 2004-03-03 15:06 ------- Subject: [Fwd: [tree-ssa] 20% compile time regression vs. 3.4] Adding to PR notes. More related C++ compile time regressions. Diego. -----Forwarded Message----- From: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de> To: gcc@gcc.gnu.org Subject: [tree-ssa] 20% compile time regression vs. 3.4 Date: Wed, 03 Mar 2004 15:46:01 +0100 Hi! I thought it was time for another 3.4 vs. tree-ssa compile-time comparison. For -O2 compile-time we regressed quite a bit (20%) with the main problem areas are (first 3.4, second tree-ssa): garbage collection : 12.19 ( 7%) usr 0.00 ( 0%) sys 12.50 ( 7%) wall garbage collection : 17.26 ( 8%) usr 0.02 ( 0%) sys 17.45 ( 8%) wall tree-ssa uses about double amount of memory parser : 14.59 ( 9%) usr 1.26 (27%) sys 16.41 ( 9%) wall parser : 18.29 ( 8%) usr 1.42 (27%) sys 19.94 ( 9%) wall I cannot make any sense out of this - are there significant changes to the parser!? Maybe that-much larger libstdc++? integration : 17.86 (11%) usr 0.29 ( 6%) sys 18.34 (10%) wall integration : 21.62 (10%) usr 0.18 ( 3%) sys 22.19 (10%) wall probably different inlining choices and finally some tree-ssa optimizer numbers stick out tree gimplify : 3.39 ( 2%) usr 0.04 ( 1%) sys 3.48 ( 1%) wall tree eh : 2.71 ( 1%) usr 0.01 ( 0%) sys 2.77 ( 1%) wall tree CFG construction : 1.69 ( 1%) usr 0.12 ( 2%) sys 1.87 ( 1%) wall tree CFG cleanup : 2.89 ( 1%) usr 0.02 ( 0%) sys 2.98 ( 1%) wall tree PTA : 0.49 ( 0%) usr 0.03 ( 1%) sys 0.52 ( 0%) wall tree alias analysis : 0.71 ( 0%) usr 0.01 ( 0%) sys 0.75 ( 0%) wall tree PHI insertion : 2.14 ( 1%) usr 0.04 ( 1%) sys 2.25 ( 1%) wall tree SSA rewrite : 2.94 ( 1%) usr 0.01 ( 0%) sys 3.03 ( 1%) wall tree SSA other : 3.77 ( 2%) usr 0.33 ( 6%) sys 4.17 ( 2%) wall tree operand scan : 2.95 ( 1%) usr 0.46 ( 8%) sys 3.51 ( 2%) wall dominator optimization: 14.06 ( 6%) usr 0.20 ( 4%) sys 14.60 ( 6%) wall tree SRA : 0.29 ( 0%) usr 0.00 ( 0%) sys 0.31 ( 0%) wall tree CCP : 2.29 ( 1%) usr 0.00 ( 0%) sys 2.39 ( 1%) wall tree split crit edges : 0.27 ( 0%) usr 0.00 ( 0%) sys 0.28 ( 0%) wall tree PRE : 6.11 ( 3%) usr 0.06 ( 1%) sys 6.40 ( 3%) wall tree linearize phis : 0.03 ( 0%) usr 0.00 ( 0%) sys 0.03 ( 0%) wall tree forward propagate: 1.37 ( 1%) usr 0.00 ( 0%) sys 1.42 ( 1%) wall tree conservative DCE : 2.71 ( 1%) usr 0.02 ( 0%) sys 2.80 ( 1%) wall tree aggressive DCE : 1.40 ( 1%) usr 0.00 ( 0%) sys 1.45 ( 1%) wall tree DSE : 3.30 ( 2%) usr 0.03 ( 1%) sys 3.42 ( 1%) wall tree copy headers : 1.80 ( 1%) usr 0.01 ( 0%) sys 1.84 ( 1%) wall tree SSA to normal : 3.18 ( 1%) usr 0.13 ( 2%) sys 3.39 ( 1%) wall tree NRV optimization : 0.01 ( 0%) usr 0.00 ( 0%) sys 0.01 ( 0%) wall tree rename SSA copies: 0.83 ( 0%) usr 0.03 ( 1%) sys 0.88 ( 0%) wall namely DOM (again) and PRE. This is with the famous tramp3d-v2.cpp testcase you can find at http://www.tat.physik.uni-tuebingen.de/~rguenth/gcc/tramp3d-v2.cpp.gz g++-ssa (GCC) 3.5-tree-ssa 20040303 (merged 20040227) g++ (GCC) 3.4.0 20040301 (prerelease) compiled with -O2 -c tramp3d-v2.cpp -Dleafify=fooblah -ftime-report to disable leafify effects. The 3.4 compiler was profiledbootstrapped while the ssa one was only bootstrapped. Of course checking was disabled. Thanks, Richard. -- Richard Guenther <richard dot guenther at uni-tuebingen dot de> WWW: http://www.tat.physik.uni-tuebingen.de/~rguenth/ -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13776
next prev parent reply other threads:[~2004-03-03 15:06 UTC|newest] Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-20 18:39 [Bug c++/13776] New: Many C++ compile-time regression in 3.5-tree-ssa 040120 in comparison with 3.4.0 040114 kgardas at objectsecurity dot com 2004-01-20 18:53 ` [Bug c++/13776] " bangerth at dealii dot org 2004-01-20 18:57 ` kgardas at objectsecurity dot com 2004-01-20 19:03 ` dhazeghi at yahoo dot com 2004-01-20 19:17 ` kgardas at objectsecurity dot com 2004-01-20 19:29 ` pinskia at gcc dot gnu dot org 2004-01-20 19:42 ` bangerth at dealii dot org 2004-01-21 23:33 ` [Bug c++/13776] [tree-ssa] " pinskia at gcc dot gnu dot org 2004-01-25 21:03 ` [Bug c++/13776] [tree-ssa] Many C++ compile-time regression in 3.5-tree-ssa 040120 mmitchel at gcc dot gnu dot org 2004-03-03 15:06 ` dnovillo at redhat dot com [this message] 2004-03-03 15:39 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-03 16:27 ` pinskia at gcc dot gnu dot org 2004-03-12 14:21 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-12 23:34 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-13 2:02 ` dberlin at dberlin dot org 2004-03-13 2:08 ` dberlin at dberlin dot org 2004-03-13 2:08 ` dnovillo at redhat dot com 2004-03-13 2:10 ` dberlin at gcc dot gnu dot org 2004-03-13 11:09 ` mattyt-bugzilla at tpg dot com dot au 2004-03-13 11:43 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-13 11:46 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-13 15:57 ` dberlin at dberlin dot org 2004-03-13 16:00 ` dberlin at dberlin dot org 2004-03-13 16:44 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-13 16:53 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-13 17:00 ` dberlin at dberlin dot org 2004-03-13 17:02 ` dberlin at dberlin dot org 2004-03-13 17:07 ` dberlin at dberlin dot org 2004-03-14 4:47 ` dberlin at gcc dot gnu dot org 2004-03-14 12:10 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-14 13:54 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-14 15:38 ` dberlin at dberlin dot org 2004-03-14 18:00 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-14 18:22 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-14 22:21 ` dberlin at dberlin dot org 2004-03-14 22:23 ` dberlin at dberlin dot org 2004-03-14 22:28 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-14 22:52 ` dberlin at gcc dot gnu dot org 2004-03-14 23:14 ` dberlin at gcc dot gnu dot org 2004-03-14 23:45 ` pinskia at gcc dot gnu dot org 2004-03-15 9:03 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-24 17:16 ` giovannibajo at libero dot it 2004-03-24 18:32 ` giovannibajo at libero dot it 2004-03-28 7:38 ` pinskia at gcc dot gnu dot org 2004-03-28 18:45 ` pinskia at gcc dot gnu dot org 2004-03-29 2:32 ` pinskia at gcc dot gnu dot org 2004-03-29 12:14 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-31 19:33 ` steven at gcc dot gnu dot org 2004-03-31 19:37 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-31 19:53 ` zack at codesourcery dot com 2004-03-31 20:01 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-03-31 20:44 ` steven at gcc dot gnu dot org 2004-04-04 12:45 ` steven at gcc dot gnu dot org 2004-04-10 14:58 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-04-10 15:32 ` Diego Novillo 2004-04-10 15:33 ` dnovillo at redhat dot com 2004-04-10 15:36 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-04-10 16:10 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-04-10 16:20 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-05-17 15:59 ` [Bug tree-optimization/13776] [3.5 Regression] " pinskia at gcc dot gnu dot org 2004-06-07 18:13 ` pinskia at gcc dot gnu dot org 2004-06-09 23:55 ` pinskia at gcc dot gnu dot org 2004-06-29 21:12 ` rth at gcc dot gnu dot org 2004-06-30 3:15 ` giovannibajo at libero dot it 2004-07-08 18:16 ` kgardas at objectsecurity dot com 2004-08-30 1:40 ` giovannibajo at libero dot it 2004-08-31 9:15 ` kgardas at objectsecurity dot com 2004-10-23 21:26 ` [Bug tree-optimization/13776] [4.0 Regression] [tree-ssa] Many C++ compile-time regression in 4.0-tree-ssa 040120 pinskia at gcc dot gnu dot org 2004-10-25 12:03 ` kgardas at objectsecurity dot com 2004-10-25 13:02 ` rguenth at tat dot physik dot uni-tuebingen dot de 2004-10-25 13:20 ` kgardas at objectsecurity dot com 2004-11-16 1:52 ` pinskia at gcc dot gnu dot org 2004-11-18 21:12 ` pinskia at gcc dot gnu dot org 2004-11-19 11:15 ` kgardas at objectsecurity dot com 2004-11-19 18:22 ` pinskia at gcc dot gnu dot org 2004-11-29 19:56 ` kgardas at objectsecurity dot com 2004-11-29 20:05 ` law at redhat dot com 2004-11-29 21:04 ` kgardas at objectsecurity dot com 2004-12-13 3:03 ` pinskia at gcc dot gnu dot org 2004-12-13 6:38 ` pinskia at gcc dot gnu dot org 2004-12-13 6:59 ` pinskia at gcc dot gnu dot org 2004-12-28 21:03 ` [Bug middle-end/13776] [4.0 Regression] " kgardas at objectsecurity dot com 2005-01-26 10:21 ` [Bug middle-end/13776] [4.0 Regression] Many C++ compile-time regressions for MICO's ORB code steven at gcc dot gnu dot org 2005-01-26 10:25 ` rguenth at tat dot physik dot uni-tuebingen dot de 2005-01-26 10:25 ` kgardas at objectsecurity dot com 2005-01-26 10:46 ` kgardas at objectsecurity dot com 2005-01-26 11:36 ` steven at gcc dot gnu dot org 2005-01-27 5:03 ` pinskia at gcc dot gnu dot org 2005-01-31 9:31 ` kgardas at objectsecurity dot com 2005-02-01 13:39 ` arend dot bayer at web dot de 2005-03-02 20:09 ` [Bug middle-end/13776] [4.0/4.1 " kgardas at objectsecurity dot com 2005-03-02 21:28 ` pinskia at gcc dot gnu dot org 2005-03-02 21:32 ` giovannibajo at libero dot it
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=20040303150639.27819.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: 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).