public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109029] __builtin_signbit for 64bit fp does not vectorize Date: Sun, 05 Mar 2023 19:18:05 +0000 [thread overview] Message-ID: <bug-109029-4-lRjZ38hrdV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109029-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109029 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Status|UNCONFIRMED |NEW Blocks| |53947 Summary|std::signbit(double) |__builtin_signbit for 64bit |generates very inefficient |fp does not vectorize |code | Component|target |tree-optimization Last reconfirmed| |2023-03-05 Ever confirmed|0 |1 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- missed: mismatched vector sizes const vector(2) double and vector(2) int Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947 [Bug 53947] [meta-bug] vectorizer missed-optimizations
next prev parent reply other threads:[~2023-03-05 19:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-05 12:08 [Bug c++/109029] New: std::signbit(double) generiert sehr ineffizienten code g.peterhoff@t-online.de 2023-03-05 12:11 ` [Bug c++/109029] " g.peterhoff@t-online.de 2023-03-05 19:18 ` pinskia at gcc dot gnu.org [this message] 2023-03-06 8:52 ` [Bug tree-optimization/109029] __builtin_signbit for 64bit fp does not vectorize rguenth at gcc dot gnu.org 2023-03-31 3:37 ` crazylht at gmail dot com 2023-03-31 4:16 ` crazylht at gmail dot com 2023-03-31 5:47 ` crazylht at gmail dot com 2023-03-31 5:52 ` crazylht at gmail dot com 2023-03-31 6:22 ` crazylht at gmail dot com 2023-03-31 7:19 ` crazylht at gmail dot com
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-109029-4-lRjZ38hrdV@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).