public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101474] SRA sometimes produces worse code with inline functions (seen with -fipa-icf sometimes) Date: Fri, 16 Jul 2021 16:42:08 +0000 [thread overview] Message-ID: <bug-101474-4-Pi2RvljnYH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101474-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101474 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|-fipa-icf generates worse |SRA sometimes produces |code for identical function |worse code with inline | |functions (seen with | |-fipa-icf sometimes) Ever confirmed|0 |1 Last reconfirmed| |2021-07-16 Status|UNCONFIRMED |NEW --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This worse code generation has nothing to do with -fipa-icf really as shown by: struct t { char x; int y; }; void fn1(struct t *p, struct t v) { *p = v; } void fn3(struct t *p, struct t v) { fn1(p, v); } ------ CUT ---- What is happening is SRA decides it is best to do a full scalar replacement for the v that is inlined into fn3 (from fn1).
next prev parent reply other threads:[~2021-07-16 16:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-16 16:33 [Bug c/101474] New: -fipa-icf generates worse code for identical function vegard.nossum at oracle dot com 2021-07-16 16:42 ` pinskia at gcc dot gnu.org [this message] 2021-07-19 6:21 ` [Bug tree-optimization/101474] SRA sometimes produces worse code with inline functions (seen with -fipa-icf sometimes) rguenth at gcc dot gnu.org 2021-11-22 6:42 ` pinskia at gcc dot gnu.org 2021-11-22 7:03 ` pinskia 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-101474-4-Pi2RvljnYH@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).