public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov/profile/24487] [3.4/4.0/4.1 Regression] Basic block frequencies inaccurate
Date: Fri, 28 Oct 2005 21:29:00 -0000	[thread overview]
Message-ID: <20051028212919.24525.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24487-327@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from hubicka at ucw dot cz  2005-10-28 21:29 -------
Subject: Re: [Bug gcov/profile/24487] [3.4/4.0/4.1 Regression] Basic block
frequencies inaccurate

> 
> 
> ------- Comment #3 from dje at gcc dot gnu dot org  2005-10-28 17:30 -------
> The misprediction causes (or at least contributes to) compute_alignments in
> final.c not aligning the critical loop in longest_match.  The recent changes to
> bb-reorder.c moved the start of the loop from an ideal alignment to the worst
> alignment, causing a 8-10% performance drop due to instruction fetch problems. 
> Without the explicit alignment directives omitted because of misprediction, the
> alignment of the loop is random.

I see, Athlon is less sensitive to alignment that might explain it.  I
will try to fix my SPEC testing setup on PPC after SVN revamp and
benchmark it there too...

Honza

> 
> 
> -- 
> 
> dje at gcc dot gnu dot org changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |dberlin at gcc dot gnu dot
>                    |                            |org
> 
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24487
> 
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
> You are the assignee for the bug, or are watching the assignee.


-- 


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


  parent reply	other threads:[~2005-10-28 21:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22 20:24 [Bug gcov/profile/24487] New: " dje at gcc dot gnu dot org
2005-10-23 20:11 ` [Bug gcov/profile/24487] [Regression 3.4/4.0/4.1] " dje at gcc dot gnu dot org
2005-10-23 20:16 ` [Bug gcov/profile/24487] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-10-24 21:36 ` dje at gcc dot gnu dot org
2005-10-28 16:32 ` hubicka at gcc dot gnu dot org
2005-10-28 17:31 ` dje at gcc dot gnu dot org
2005-10-28 21:29 ` hubicka at ucw dot cz [this message]
2005-10-31  6:39 ` mmitchel at gcc dot gnu dot org
2005-10-31 14:49 ` hubicka at gcc dot gnu dot org
2005-10-31 14:54 ` hubicka at gcc dot gnu dot org
2005-11-03  8:22 ` [Bug gcov/profile/24487] [3.4/4.0 " hubicka 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=20051028212919.24525.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).