public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102473] [12 Regression] 521.wrf_r 5% slower at -Ofast and generic x86_64 tuning after r12-3426-g8f323c712ea76c
Date: Tue, 28 Sep 2021 02:59:17 +0000 [thread overview]
Message-ID: <bug-102473-4-TKb1RcCC4j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102473-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102473
--- Comment #15 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to H.J. Lu from comment #14)
> (In reply to Hongtao.liu from comment #13)
> > (In reply to H.J. Lu from comment #12)
> > > Are glibc regressions real? Please show the affected glibc assembly codes
> > > before and after.
> >
> > Assembly codes is the same, but DSB coverage drop down. before my commit
> > front-end bound of libc-2.31.so is 1.2%, after my commit front-end bound
> > raise up to 21.9%, use -falign-functions=64 doesn't help.
> >
> > The below code is copy from one of libc functions which has big front-end
> > bounds
> >
>
> Which functions in glibc get lower DSB coverage?
About a dozen small functions have been affected, no symbol info, the second
column is time(seconds)
func@0x5eed4 1.77755
func@0x58de4 1.53788
func@0x76f20 0.963671
func@0x5ea50 0.758953
func@0x83750 0.349518
func@0x60d59 0.284607
func@0x799e4 0.164773
func@0x59b64 0.15978
func@0x8f070 0.1448
next prev parent reply other threads:[~2021-09-28 2:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 16:45 [Bug target/102473] New: " jamborm at gcc dot gnu.org
2021-09-24 6:52 ` [Bug target/102473] [12 Regression] " rguenth at gcc dot gnu.org
2021-09-24 7:39 ` crazylht at gmail dot com
2021-09-24 7:50 ` rguenth at gcc dot gnu.org
2021-09-24 10:43 ` crazylht at gmail dot com
2021-09-26 7:29 ` crazylht at gmail dot com
2021-09-27 2:01 ` crazylht at gmail dot com
2021-09-27 2:16 ` crazylht at gmail dot com
2021-09-27 7:49 ` crazylht at gmail dot com
2021-09-27 7:51 ` cvs-commit at gcc dot gnu.org
2021-09-27 8:10 ` jamborm at gcc dot gnu.org
2021-09-27 8:18 ` crazylht at gmail dot com
2021-09-27 14:27 ` hjl.tools at gmail dot com
2021-09-28 2:20 ` crazylht at gmail dot com
2021-09-28 2:24 ` hjl.tools at gmail dot com
2021-09-28 2:59 ` crazylht at gmail dot com [this message]
2022-01-20 9:53 ` rguenth at gcc dot gnu.org
2022-05-06 8:31 ` [Bug target/102473] [12/13 " jakub at gcc dot gnu.org
2022-07-26 13:27 ` 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-102473-4-TKb1RcCC4j@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).