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/108874] [10/11/12/13 Regression] Missing bswap detection Date: Wed, 22 Feb 2023 08:37:42 +0000 [thread overview] Message-ID: <bug-108874-4-aWlmCFHaLC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108874-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108874 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-bisection Version|unknown |13.0 Target Milestone|--- |10.5 Component|tree-optimization |target Target| |arm --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- The regression is probably rtl-optimization/target specific since we never had this kind of pattern detected on the tree/GIMPLE level and there's no builtin or IFN for this shuffling on u32.
next prev parent reply other threads:[~2023-02-22 8:37 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-21 16:30 [Bug tree-optimization/108874] New: " ktkachov at gcc dot gnu.org 2023-02-21 16:53 ` [Bug tree-optimization/108874] " ktkachov at gcc dot gnu.org 2023-02-22 8:37 ` rguenth at gcc dot gnu.org [this message] 2023-02-22 10:39 ` [Bug target/108874] " ktkachov at gcc dot gnu.org 2023-02-22 10:53 ` rguenth at gcc dot gnu.org 2023-02-23 23:32 ` pinskia at gcc dot gnu.org 2023-02-25 19:51 ` pinskia at gcc dot gnu.org 2023-02-27 3:24 ` crazylht at gmail dot com 2023-02-27 4:39 ` pinskia at gcc dot gnu.org 2023-03-09 23:03 ` pinskia at gcc dot gnu.org 2023-03-10 0:39 ` pinskia at gcc dot gnu.org 2023-03-10 1:04 ` pinskia at gcc dot gnu.org 2023-03-10 6:04 ` pinskia at gcc dot gnu.org 2023-03-10 17:52 ` cvs-commit at gcc dot gnu.org 2023-03-10 17:54 ` 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-108874-4-aWlmCFHaLC@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).