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 ipa/103227] 58% exchange2 regression with -Ofast -march=native on zen3 between g:1ae8edf5f73ca5c3 and g:2af63f0f53a12a72 Date: Sat, 13 Nov 2021 22:00:46 +0000 [thread overview] Message-ID: <bug-103227-4-elzBIygSGo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103227-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103227 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org, | |marxin at gcc dot gnu.org, | |mjambor at suse dot cz Last reconfirmed| |2021-11-13 Status|UNCONFIRMED |NEW Component|tree-optimization |ipa Ever confirmed|0 |1 --- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> --- So code size is due to ipa-icf: hubicka@lomikamen:/aux/hubicka/trunk/build6/gcc$ /aux/hubicka/trunk-install-fortran/bin/gfortran -Ofast -march=native -flto 548.exchange2_r/src/exchange2.F90 size a.out hubicka@lomikamen:/aux/hubicka/trunk/build6/gcc$ size a.out text data bss dec hex filename 245442 864 6368 252674 3db02 a.out hubicka@lomikamen:/aux/hubicka/trunk/build6/gcc$ /aux/hubicka/trunk-install-fortran/bin/gfortran -Ofast -march=native -flto 548.exchange2_r/src/exchange2.F90 -fno-ipa-icf -fno-ipa-modref hubicka@lomikamen:/aux/hubicka/trunk/build6/gcc$ size a.out text data bss dec hex filename 178982 864 6336 186182 2d746 a.out hubicka@lomikamen:/aux/hubicka/trunk/build6/gcc$ /aux/hubicka/trunk-install-fortran/bin/gfortran -Ofast -march=native -flto 548.exchange2_r/src/exchange2.F90 -fno-ipa-icf hubicka@lomikamen:/aux/hubicka/trunk/build6/gcc$ size a.out text data bss dec hex filename 245442 864 6368 252674 3db02 a.out We end up with isra clones of digits_2: bb/a.ltrans0.ltrans.250t.optimized:;; Function digits_2.constprop.isra (__brute_force_MOD_digits_2.constprop.6.isra.0, funcdef_no=29, decl_uid=4805, cgraph_uid=32, symbol_order=157) bb/a.ltrans1.ltrans.250t.optimized:;; Function digits_2.constprop.isra (__brute_force_MOD_digits_2.constprop.4.isra.0, funcdef_no=2, decl_uid=4730, cgraph_uid=3, symbol_order=159) bb/a.ltrans1.ltrans.250t.optimized:;; Function digits_2.constprop.isra (__brute_force_MOD_digits_2.constprop.2.isra.0, funcdef_no=6, decl_uid=4737, cgraph_uid=7, symbol_order=161) bb/a.ltrans1.ltrans.250t.optimized:;; Function digits_2.constprop.isra (__brute_force_MOD_digits_2.constprop.0.isra.0, funcdef_no=10, decl_uid=4741, cgraph_uid=11, symbol_order=163) bb/a.ltrans1.ltrans.250t.optimized:;; Function rearrange.isra (__brute_force_MOD_rearrange.isra.0, funcdef_no=14, decl_uid=4744, cgraph_uid=15, symbol_order=165) Curious is that original has 3 clones a.ltrans0.ltrans.250t.optimized:;; Function digits_2.constprop (__brute_force_MOD_digits_2.constprop.3, funcdef_no=2, decl_uid=4799, cgraph_uid=27, symbol_order=143) a.ltrans0.ltrans.250t.optimized:;; Function digits_2.constprop (__brute_force_MOD_digits_2.constprop.0, funcdef_no=5, decl_uid=4796, cgraph_uid=24, symbol_order=140) a.ltrans1.ltrans.250t.optimized:;; Function digits_2.constprop (__brute_force_MOD_digits_2.constprop.6, funcdef_no=5, decl_uid=4760, cgraph_uid=2, symbol_order=146) which likely explain the code size difference. The ipa-cp decisions are same so it looks like isra is affecting inliner which instead of producing 3 function for clones 0,3,6 produces 4 functions for clones 0,2,4,6
next prev parent reply other threads:[~2021-11-13 22:00 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-13 21:05 [Bug tree-optimization/103227] New: " hubicka at gcc dot gnu.org 2021-11-13 22:00 ` hubicka at gcc dot gnu.org [this message] 2021-11-13 22:11 ` [Bug ipa/103227] " hubicka at gcc dot gnu.org 2021-11-13 22:15 ` hubicka at gcc dot gnu.org 2021-11-15 9:04 ` [Bug ipa/103227] [12 Regression] 58% exchange2 regression with -Ofast -march=native on zen3 since r12-5223-gecdf414bd89e6ba251f6b3f494407139b4dbae0e rguenth at gcc dot gnu.org 2021-11-19 18:18 ` jamborm at gcc dot gnu.org 2021-11-19 21:12 ` hubicka at kam dot mff.cuni.cz 2021-11-19 21:22 ` hubicka at gcc dot gnu.org 2021-11-19 23:21 ` jamborm at gcc dot gnu.org 2021-11-20 12:32 ` hubicka at kam dot mff.cuni.cz 2021-11-20 12:39 ` hubicka at kam dot mff.cuni.cz 2021-11-21 15:16 ` cvs-commit at gcc dot gnu.org 2021-11-23 17:02 ` jamborm at gcc dot gnu.org 2021-11-24 12:52 ` jamborm at gcc dot gnu.org 2021-11-25 17:17 ` cvs-commit at gcc dot gnu.org 2021-11-26 9:19 ` hubicka at gcc dot gnu.org 2021-11-28 18:56 ` hubicka at gcc dot gnu.org 2022-12-14 0:04 ` cvs-commit at gcc dot gnu.org 2023-08-15 15:45 ` jamborm 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-103227-4-elzBIygSGo@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: linkBe 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).