public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/46939] http://blog.regehr.org/archives/320 example 6
Date: Wed, 15 Dec 2010 12:24:00 -0000 [thread overview]
Message-ID: <bug-46939-4-ADRUa4f5lC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46939-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46939
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2010.12.15 12:24:34
Ever Confirmed|0 |1
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> 2010-12-15 12:24:34 UTC ---
Predictions for bb 6
DS theory heuristics: 4.0%
first match heuristics (ignored): 4.0%
combined heuristics: 4.0%
negative return heuristics: 4.0%
So it is negative return heuristics.
Richi's profiling reorg broke statistics code, so I will need to dig into
archives before I fix it again. But last time I updated the tables the
heuristics was 96% right on SPEC. I am not terribly oposed in making it less
reliable with a comment explaining why. In SPEC it is most surely perfoming
heuristics, we have only few of them above 60%
The heuristics makes a guess that negative return values tends to be used to
return error stages. It is not true in this case.
next prev parent reply other threads:[~2010-12-15 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 14:31 [Bug ada/46939] New: " jakub at gcc dot gnu.org
2010-12-15 12:24 ` hubicka at gcc dot gnu.org [this message]
2010-12-15 12:54 ` [Bug ada/46939] " hubicka at gcc dot gnu.org
2010-12-15 13:29 ` hubicka at gcc dot gnu.org
2010-12-16 1:27 ` [Bug tree-optimization/46939] " hubicka at gcc dot gnu.org
2010-12-16 1:40 ` hubicka at gcc dot gnu.org
2010-12-16 9:26 ` jakub at gcc dot gnu.org
2010-12-16 15:11 ` regehr at cs dot utah.edu
2010-12-17 17:11 ` regehr at cs dot utah.edu
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=bug-46939-4-ADRUa4f5lC@http.gcc.gnu.org/bugzilla/ \
--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).