public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/113597] [14 Regression] aarch64: Significant code quality regression since r14-8346-ga98d5130a6dcff Date: Thu, 25 Jan 2024 11:40:02 +0000 [thread overview] Message-ID: <bug-113597-4-o4NdfM9W3z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113597-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113597 --- Comment #9 from Alex Coplan <acoplan at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #8) > (In reply to Alex Coplan from comment #7) > > I expect the store pairs come from memcpy lowering/expansion in the aarch64 > > backend, that is the only way we get store pairs so early in the RTL > > pipeline IIRC. > > In this case, memset is more likely. Right, yeah. I was using "memcpy lowering" to refer to all the mem{cpy,set,move} expansion we have in the backend. > > Either: > for (int i = 0; i < j; i++) > m[i] = vdupq_n_f32(0.F); > Or > for (int i = 0; i < l; i++) > n[i] = vdupq_n_f32(0.F);
next prev parent reply other threads:[~2024-01-25 11:40 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-25 10:53 [Bug rtl-optimization/113597] New: " acoplan at gcc dot gnu.org 2024-01-25 11:01 ` [Bug rtl-optimization/113597] " rguenth at gcc dot gnu.org 2024-01-25 11:01 ` rguenth at gcc dot gnu.org 2024-01-25 11:05 ` acoplan at gcc dot gnu.org 2024-01-25 11:10 ` acoplan at gcc dot gnu.org 2024-01-25 11:10 ` acoplan at gcc dot gnu.org 2024-01-25 11:16 ` pinskia at gcc dot gnu.org 2024-01-25 11:27 ` acoplan at gcc dot gnu.org 2024-01-25 11:32 ` acoplan at gcc dot gnu.org 2024-01-25 11:38 ` pinskia at gcc dot gnu.org 2024-01-25 11:40 ` acoplan at gcc dot gnu.org [this message] 2024-01-25 11:56 ` rguenth at gcc dot gnu.org 2024-01-25 13:41 ` rguenth at gcc dot gnu.org 2024-01-25 14:03 ` rguenth at gcc dot gnu.org 2024-01-29 13:56 ` rguenth at gcc dot gnu.org 2024-03-07 20:45 ` law at gcc dot gnu.org 2024-05-07 7:44 ` [Bug rtl-optimization/113597] [14/15 " 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-113597-4-o4NdfM9W3z@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).