public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/95962] Inefficient code for simple arm_neon.h iota operation Date: Fri, 03 Dec 2021 17:05:25 +0000 [thread overview] Message-ID: <bug-95962-4-V6BOCzjLlw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95962-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95962 --- Comment #4 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- (In reply to Tamar Christina from comment #3) > This is now fixed on trunk, at least for ld1/st1. Nice! > Was this ticket about the general problem for loads or just the ld1/st1 > examples? > > I'll leave it open since we still need to do the rest of the loads/stores. Yeah, agree we should keep it open for {ld,st}[234].
prev parent reply other threads:[~2021-12-03 17:05 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-29 12:49 [Bug target/95962] New: " rsandifo at gcc dot gnu.org 2021-08-12 8:01 ` [Bug target/95962] " tnfchris at gcc dot gnu.org 2021-08-20 11:52 ` rsandifo at gcc dot gnu.org 2021-11-15 15:09 ` tnfchris at gcc dot gnu.org 2021-12-03 17:05 ` rsandifo at gcc dot gnu.org [this message]
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-95962-4-V6BOCzjLlw@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).