public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/15524] [4.0 Regression] jump threading on trees is slow with switch statements with large # of cases
Date: Mon, 01 Nov 2004 14:09:00 -0000	[thread overview]
Message-ID: <20041101140924.8994.qmail@sourceware.org> (raw)
In-Reply-To: <20040518194300.15524.pinskia@gcc.gnu.org>


------- Additional Comments From law at redhat dot com  2004-11-01 14:09 -------
Subject: Re:  [4.0 Regression] jump threading
	on trees is slow with switch statements with large # of cases

On Mon, 2004-11-01 at 05:16 +0000, pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org  2004-11-01 05:16 -------
> We are still way behind 3.3, it takes 15 seconds on my 1.5GHz PPC 7400 with 3.3 but with 4.0, well for 
> 4.0 time just look at Jeff's data and see that we are way behind still.
Well, I haven't looked at 3.3, but I can make a reasonable guess that
we're still way way way behind due to the way we update case labels
when forwarding edges and splitting critical edges.  Some early 
experiments I've done with that indicate there's another 30-35%
improvement that can be made by fixing that problem.  Then there's
*another* 30% or so we're burning in the RTL branch prediction code
(I haven't looked to see if there's anything we can do with that code
yet).

I doubt it makes much sense to look closely at 3.3 vs 4.0 for this
testcase and similar code until we fix those glaring problems.

It's also not clear to me how much of an improvement those changes
will make in real-world code.  ie, we could easily run into a case
where we drastically improve that testcase without improving any
real code, much like what happened recently with my changes to 
improve how we find/record equivalences for edges.

Jeff



-- 


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


  parent reply	other threads:[~2004-11-01 14:09 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 12:56 [Bug tree-optimization/15524] New: [3.5 " pinskia at gcc dot gnu dot org
2004-05-19 12:57 ` [Bug tree-optimization/15524] " pinskia at gcc dot gnu dot org
2004-05-19 13:06 ` pinskia at gcc dot gnu dot org
2004-05-19 17:45 ` pinskia at gcc dot gnu dot org
2004-05-25 15:47 ` pinskia at gcc dot gnu dot org
2004-05-25 15:48 ` pinskia at gcc dot gnu dot org
2004-05-26 15:03 ` steven at gcc dot gnu dot org
2004-05-26 17:09 ` steven at gcc dot gnu dot org
2004-05-27  9:33 ` pinskia at gcc dot gnu dot org
2004-07-13 17:03 ` steven at gcc dot gnu dot org
2004-07-27 18:04 ` steven at gcc dot gnu dot org
2004-09-18  0:23 ` [Bug tree-optimization/15524] [4.0 " steven at gcc dot gnu dot org
2004-09-24 10:29 ` dnovillo at redhat dot com
2004-09-24 16:04 ` law at redhat dot com
2004-10-03 21:01 ` phython at gcc dot gnu dot org
2004-10-06 19:58 ` law at redhat dot com
2004-10-08 21:36 ` pinskia at gcc dot gnu dot org
2004-11-01  3:51 ` dberlin at dberlin dot org
2004-11-01  3:52 ` giovannibajo at libero dot it
2004-11-01  5:16 ` pinskia at gcc dot gnu dot org
2004-11-01 14:09 ` law at redhat dot com [this message]
2004-11-01 15:03 ` s dot bosscher at student dot tudelft dot nl
2004-11-01 16:56 ` giovannibajo at libero dot it
2004-11-01 19:35 ` kazu at cs dot umass dot edu
2004-11-01 20:04 ` law at redhat dot com
2004-11-01 20:17 ` stevenb at suse dot de
2004-11-01 21:19 ` law at redhat dot com
2004-11-01 21:19 ` law at redhat dot com
2004-11-01 21:22 ` stevenb at suse dot de
2004-11-03 15:09 ` pinskia at physics dot uc dot edu
2004-11-03 15:43 ` law at redhat dot com
2004-11-03 15:44 ` richard dot guenther at gmail dot com
2004-11-03 16:33 ` kazu at cs dot umass dot edu
2004-11-03 16:46 ` law at redhat dot com
2004-11-03 16:51 ` kazu at cs dot umass dot edu
2004-11-03 16:52 ` s dot bosscher at student dot tudelft dot nl
2004-11-04  0:29 ` stevenb at suse dot de
2004-11-04  0:29 ` steven at gcc dot gnu dot org
2004-11-07 22:13 ` steven at gcc dot gnu dot org
2004-11-11 21:42 ` law at redhat dot com
2004-11-18 13:00 ` pinskia at gcc dot gnu dot org
2004-11-18 13:00 ` pinskia at gcc dot gnu dot org
2004-11-18 14:31 ` pinskia at gcc dot gnu dot org
2004-11-18 15:57 ` law at redhat dot com
2004-11-18 18:24 ` pinskia at gcc dot gnu dot org
2004-11-19  3:14 ` law at redhat dot com
2004-11-20 20:32 ` ebotcazou at libertysurf dot fr
2004-11-20 20:39 ` law at redhat dot com
2004-11-21  7:13 ` ebotcazou at libertysurf dot fr
2004-11-21 21:55 ` pinskia at gcc dot gnu dot org
2004-11-21 22:18 ` law at redhat dot com
2004-11-21 22:54 ` giovannibajo at libero dot it
2004-11-22 17:16 ` law at redhat dot com
2004-12-04 15:35 ` pinskia at gcc dot gnu dot org
2004-12-20  0:51 ` steven at gcc dot gnu dot org
2004-12-21  6:23 ` law at redhat dot com
2004-12-22 19:18 ` steven at gcc dot gnu dot org
2004-12-22 19:28 ` law at redhat dot com
2004-12-23 13:31 ` steven at gcc dot gnu dot org
2004-12-23 17:22 ` law at redhat dot com
2005-01-28 14:28 ` pinskia at gcc dot gnu dot org
2005-04-08 21:49 ` dnovillo at gcc dot gnu dot org
2005-04-12 16:55 ` law at redhat dot com
2005-04-13 13:03   ` Diego Novillo
2005-04-13 13:04 ` dnovillo at redhat dot com
2005-04-13 17:11 ` law at redhat dot com

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