public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/66004] [6 Regression]: performance of 26_numerics/random/negative_binomial_distribution/operators/values.cc
Date: Wed, 06 May 2015 04:47:00 -0000 [thread overview]
Message-ID: <bug-66004-4-N2c7y0Ap7o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66004-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66004
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
Component|libstdc++ |ipa
--- Comment #2 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
Bisecting shows that revision r221859 is the culprit, adding Honza to CC.
I hope to add analysis of the compiled code showing (an example of) the
regressed code, but it would be really nice if Someone could
performance-regression test r221859 (compared to r221858) on another target.
Weird that a performance-regression of 16% is supposed to be *fixed* by that
commit (see PR65076). While it refers to *compile-time* regression, that is
just another name for a *run-time* performance-regression of the bootstrapped
compiler, apparently typical for at least the execution-path when compiling
tramp3d-v4.cpp supposedly for x86_64-linux and
26_numerics/random/negative_binomial_distribution/operators/values.cc for
cris-elf.
Note that the regression is not fixed for cris-elf at r222305 (a later
additional commit referencing PR65076).
Revision-numbers and cycle numbers while bisecting follows. Note the very
stable numbers:
r221618 34633750695
r221758 34633750695
r221828 34633750695
r221845 34633750695
r221854 34633750695
r221858 34633750695
r221859 40068917595
r221860 40068917595
r221863 40068917595
r221899 40068917595
r222180 40068917595
r222742 40111446541
next prev parent reply other threads:[~2015-05-06 4:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-66004-4@http.gcc.gnu.org/bugzilla/>
2015-05-04 13:03 ` [Bug libstdc++/66004] " rguenth at gcc dot gnu.org
2015-05-04 17:20 ` hp at gcc dot gnu.org
2015-05-06 4:47 ` hp at gcc dot gnu.org [this message]
2015-05-16 1:04 ` [Bug ipa/66004] " hp at gcc dot gnu.org
2021-05-14 9:47 ` [Bug ipa/66004] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:06 ` rguenth at gcc dot gnu.org
2022-05-27 9:35 ` [Bug ipa/66004] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:31 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug ipa/66004] [11/12/13/14 " rguenth at gcc dot gnu.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=bug-66004-4-N2c7y0Ap7o@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).