public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at kam dot mff.cuni.cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103223] [12 regression] Access attribute dropped when ipa-sra is applied
Date: Mon, 22 Nov 2021 07:53:06 +0000 [thread overview]
Message-ID: <bug-103223-4-bNVVHTedl0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103223-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103223
--- Comment #11 from hubicka at kam dot mff.cuni.cz ---
> Xeon(R) Platinum 8358 (IceLake) (64C 128T 512G):
> BenchMarks Copies RunTime1 RunTime2 Rate1 Rate2 Compare
> 548.exchange2_r 128 479 913 700 367 -47.57%
>
> Xeon(R) Gold 6252 (CascadeLake) (48C 96T 192G)
> BenchMarks Copies RunTime1 RunTime2 Rate1 Rate2 Compare
> 548.exchange2_r 96 643 1240 391 203 -48.08%
I filled in PR103227 to track this problem. There seems to be two
issues visible on exchange2. First is that ipa-sra changes order of
functions which in which inliner visits them and this makes difference
in inlining decisions. Second is that ipa-sra makes some constant
propagation info to be lost. With Martin we look into this.
next prev parent reply other threads:[~2021-11-22 7:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 10:05 [Bug tree-optimization/103223] New: [12 regression] Access attribute prevents IPA optimization hubicka at gcc dot gnu.org
2021-11-13 23:56 ` [Bug tree-optimization/103223] [12 regression] Access attribute dropped when ipa-sra is applied hubicka at gcc dot gnu.org
2021-11-15 9:02 ` rguenth at gcc dot gnu.org
2021-11-15 15:50 ` jamborm at gcc dot gnu.org
2021-11-15 15:58 ` jamborm at gcc dot gnu.org
2021-11-15 16:12 ` msebor at gcc dot gnu.org
2021-11-15 18:12 ` jamborm at gcc dot gnu.org
2021-11-15 20:19 ` msebor at gcc dot gnu.org
2021-11-15 21:02 ` hubicka at kam dot mff.cuni.cz
2021-11-15 22:32 ` msebor at gcc dot gnu.org
2021-11-22 7:35 ` admin at levyhsu dot com
2021-11-22 7:53 ` hubicka at kam dot mff.cuni.cz [this message]
2022-05-06 8:31 ` [Bug ipa/103223] [12/13 " jakub at gcc dot gnu.org
2023-05-08 12:23 ` [Bug ipa/103223] [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-103223-4-bNVVHTedl0@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).