public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115487] -march=cascadelake causes spilling Date: Fri, 14 Jun 2024 09:42:18 +0000 [thread overview] Message-ID: <bug-115487-4-EyjVD3JH9Q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115487-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115487 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- It looks like it's STV2 doing 28: r131:V4SI=[r102:SI] 30: r132:V4SI=[r102:SI+0x10] 33: r133:DI=vec_select(r131:V4SI#0,parallel) - 34: [r103:SI]=r133:DI + 92: r143:DI#0=vec_merge(vec_duplicate(r133:DI#0),const_vector,0x1) + 93: r144:DI#0=vec_merge(vec_duplicate(r133:DI#4),const_vector,0x1) + 94: r143:DI#0=vec_select(vec_concat(r143:DI#0,r144:DI#0),parallel) + 89: r141:DI#0=vec_merge(vec_duplicate(r133:DI#0),const_vector,0x1) + 90: r142:DI#0=vec_merge(vec_duplicate(r133:DI#4),const_vector,0x1) + 91: r141:DI#0=vec_select(vec_concat(r141:DI#0,r142:DI#0),parallel) + 34: [r103:SI]=r141:DI 36: [r103:SI+0x8]=vec_select(r131:V4SI#0,parallel) REG_DEAD r131:V4SI - 38: [r103:SI+0x10]=r133:DI - REG_DEAD r133:DI + 38: [r103:SI+0x10]=r143:DI + REG_DEAD r143:DI for some weird reason and that later causes spilling. I'll also note that STV2 doesn't seem to recog any of the created insns.
next prev parent reply other threads:[~2024-06-14 9:42 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-14 9:31 [Bug target/115487] New: " rguenth at gcc dot gnu.org 2024-06-14 9:42 ` rguenth at gcc dot gnu.org [this message] 2024-06-14 9:59 ` [Bug target/115487] " 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-115487-4-EyjVD3JH9Q@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).