public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/15855] [3.4/4.0 Regression] g++ crash with -O2 and -O3 on input file
Date: Sun, 21 Nov 2004 05:33:00 -0000 [thread overview]
Message-ID: <20041121053343.4504.qmail@sourceware.org> (raw)
In-Reply-To: <20040606191038.15855.abegel@cs.berkeley.edu>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-21 05:33 -------
These part are 4.0 regressions:
tree alias analysis : 24.22 ( 6%) usr 0.75 ( 2%) sys 26.57 ( 5%) wall
tree PHI insertion : 7.71 ( 2%) usr 1.26 ( 3%) sys 9.24 ( 2%) wall
tree SSA rewrite : 11.52 ( 3%) usr 4.32 (11%) sys 20.63 ( 4%) wall
tree SSA other : 21.33 ( 5%) usr 3.77 (10%) sys 27.79 ( 5%) wall
tree operand scan : 26.65 ( 7%) usr 3.78 (10%) sys 31.64 ( 6%) wall
These are most likely not:
combiner : 25.57 ( 6%) usr 0.20 ( 1%) sys 26.78 ( 5%) wall
scheduling : 211.44 (52%) usr 4.35 (11%) sys 225.27 (43%) wall
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15855
next prev parent reply other threads:[~2004-11-21 5:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 19:10 [Bug c++/15855] New: " abegel at cs dot berkeley dot edu
2004-06-06 19:12 ` [Bug c++/15855] " abegel at cs dot berkeley dot edu
2004-06-06 19:18 ` pinskia at gcc dot gnu dot org
2004-06-06 19:25 ` pinskia at gcc dot gnu dot org
2004-06-06 19:39 ` abegel at cs dot berkeley dot edu
2004-08-15 3:27 ` [Bug rtl-optimization/15855] " pinskia at gcc dot gnu dot org
2004-08-15 3:28 ` [Bug rtl-optimization/15855] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-08-29 18:47 ` mmitchel at gcc dot gnu dot org
2004-10-12 13:26 ` [Bug rtl-optimization/15855] [3.4/4.0 " pinskia at gcc dot gnu dot org
2004-10-12 13:28 ` [Bug c++/15855] " pinskia at gcc dot gnu dot org
2004-10-12 13:29 ` [Bug middle-end/15855] " pinskia at gcc dot gnu dot org
2004-11-01 0:45 ` mmitchel at gcc dot gnu dot org
2004-11-21 5:33 ` pinskia at gcc dot gnu dot org [this message]
2004-11-21 5:54 ` pinskia at gcc dot gnu dot org
2004-11-23 3:49 ` pinskia at gcc dot gnu dot org
2004-11-23 3:51 ` giovannibajo at libero dot it
2004-11-25 20:29 ` pinskia at gcc dot gnu dot org
2004-11-26 16:01 ` pinskia at gcc dot gnu dot org
2004-11-27 7:50 ` law at redhat dot com
2004-11-27 8:18 ` giovannibajo at libero dot it
2004-11-27 16:57 ` law at redhat dot com
2004-11-28 23:52 ` giovannibajo at libero dot it
2004-12-01 18:32 ` rth at redhat dot com
2004-12-02 6:09 ` rth at redhat dot com
2004-12-02 15:57 ` law at redhat dot com
2004-12-22 19:20 ` steven at gcc dot gnu dot org
2004-12-22 19:29 ` law at redhat dot com
2005-05-19 17:23 ` [Bug middle-end/15855] [3.4/4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-07-22 21:16 ` pinskia at gcc dot gnu dot org
2005-07-24 1:00 ` pinskia at gcc dot gnu dot org
2005-08-12 6:21 ` phython at gcc dot gnu dot org
2005-08-12 19:08 ` wilson at specifix dot com
2005-09-12 10:53 ` rguenth at gcc dot gnu dot org
2005-09-15 22:06 ` rguenth at gcc dot gnu dot org
2005-09-16 8:14 ` rguenth at gcc dot gnu dot org
2005-09-26 8:39 ` cvs-commit at gcc dot gnu dot org
2005-09-26 8:43 ` cvs-commit at gcc dot gnu dot org
2005-09-27 15:59 ` 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=20041121053343.4504.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: 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).