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 tree-optimization/18687] [4.0 Regression] ~50% compile time regression
Date: Tue, 30 Nov 2004 14:32:00 -0000	[thread overview]
Message-ID: <20041130143252.21164.qmail@sourceware.org> (raw)
In-Reply-To: <20041127043006.18687.belyshev@lubercy.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-11-30 14:32 -------
At -O2 and -O3 also I see is_attribute_p is always taking 2% of the time.
At -O0:
- is_attribute_p -  6%
- decode_reg_name - 2.1%
at -O1:
- is_attribute_p -  2.5%
- decode_reg_name 0.8%
at -O2:
 - is_attribute_p -  1.9%
- decode_reg_name  - 0.5%
at -O3 (this was a bigger sample than the obove ones):
- is_attribute_p -  1.8%
- decode_reg_name - 0.6%


-- 


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


  parent reply	other threads:[~2004-11-30 14:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27  4:30 [Bug tree-optimization/18687] New: " belyshev at lubercy dot com
2004-11-27  4:31 ` [Bug tree-optimization/18687] " belyshev at lubercy dot com
2004-11-27  4:32 ` belyshev at lubercy dot com
2004-11-27  4:42 ` pinskia at gcc dot gnu dot org
2004-11-27 15:47 ` pinskia at gcc dot gnu dot org
2004-11-27 18:44 ` belyshev at lubercy dot com
2004-11-30 13:09 ` pinskia at gcc dot gnu dot org
2004-11-30 13:11 ` pinskia at gcc dot gnu dot org
2004-11-30 14:32 ` pinskia at gcc dot gnu dot org [this message]
2004-11-30 14:57 ` pinskia at gcc dot gnu dot org
2004-11-30 15:17 ` pinskia at gcc dot gnu dot org
2004-12-02 14:06 ` pinskia at gcc dot gnu dot org
2004-12-02 15:27 ` pinskia at gcc dot gnu dot org
2004-12-03  0:24 ` belyshev at lubercy dot com
     [not found] <20041127043006.18687.belyshev@depni.sinp.msu.ru>
2004-12-22 21:50 ` belyshev at depni dot sinp dot msu dot ru
2005-01-28  0:55 ` steven at gcc dot gnu dot org
2005-01-30 22:53 ` steven at gcc dot gnu dot org
2005-01-30 22:55 ` steven at gcc dot gnu dot org
2005-01-30 23:42 ` steven at gcc dot gnu dot org
2005-02-08 13:54 ` rakdver at gcc dot gnu dot org
2005-02-09  0:48 ` rakdver at gcc dot gnu dot org
2005-02-10  6:28 ` cvs-commit at gcc dot gnu dot org
2005-02-10  9:49 ` pinskia at gcc dot gnu dot org
2005-02-10 20:32 ` belyshev at depni dot sinp dot msu dot ru

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=20041130143252.21164.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).