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 tree-optimization/109240] Missed fneg/fsub optimization Date: Wed, 22 Mar 2023 07:43:48 +0000 [thread overview] Message-ID: <bug-109240-4-cezUv8OI1U@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109240-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109240 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- You can try if match.pd is "preprocessed enough" to make use of macros. vec_perm:c cannot be done, "selective" :c on a for iterator is also not possible. If you have an idea for a syntax to express the "iteration" please share it.
next prev parent reply other threads:[~2023-03-22 7:43 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-21 19:25 [Bug tree-optimization/109240] New: " jakub at gcc dot gnu.org 2023-03-22 7:43 ` rguenth at gcc dot gnu.org [this message] 2023-03-22 9:39 ` [Bug tree-optimization/109240] " jakub at gcc dot gnu.org 2023-03-26 18:44 ` jakub at gcc dot gnu.org 2023-04-18 9:02 ` cvs-commit at gcc dot gnu.org 2023-04-18 9:03 ` jakub 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-109240-4-cezUv8OI1U@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).