public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manolis.tsamis at vrull dot eu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114010] Unwanted effects of using SSA free lists. Date: Wed, 21 Feb 2024 12:09:59 +0000 [thread overview] Message-ID: <bug-114010-4-lxDsyGRz9l@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114010-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114010 --- Comment #5 from Manolis Tsamis <manolis.tsamis at vrull dot eu> --- Also, I further investigated the codegen difference in the second example (zip + umlal vs umull) and it looks to be some sort of RTL ordering + combine issue. Specifically, when the we expand the RTL for the example there are some very slight ordering differences where some non-dependent insns have swapped order. On of these happens to precede a relevant vector statement and then in one case combine does the umlal transformation but in the other not. Afaik combine has some limits about the instruction window that it looks, so it looks feasible that ordering differences in RTL can later transform into major codegen differences in a number of ways. Other differences seem to come from register allocation, as you mentioned. This doesn't yet provide any useful insights whether the vectorization improvements are accidental or not.
next prev parent reply other threads:[~2024-02-21 12:09 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-20 10:22 [Bug tree-optimization/114010] New: " manolis.tsamis at vrull dot eu 2024-02-21 0:06 ` [Bug tree-optimization/114010] " pinskia at gcc dot gnu.org 2024-02-21 0:11 ` pinskia at gcc dot gnu.org 2024-02-21 0:22 ` pinskia at gcc dot gnu.org 2024-02-21 12:03 ` manolis.tsamis at vrull dot eu 2024-02-21 12:09 ` manolis.tsamis at vrull dot eu [this message] 2024-02-22 1:02 ` ptomsich at gcc dot gnu.org 2024-02-22 1:02 ` ptomsich at gcc dot gnu.org 2024-02-22 10:28 ` rguenth at gcc dot gnu.org 2024-02-23 14:31 ` ptomsich at gcc dot gnu.org 2024-02-23 15:02 ` manolis.tsamis at vrull dot eu
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-114010-4-lxDsyGRz9l@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).