public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109829] Optimizing __builtin_signbit(x) ? -x : x or abs for FP Date: Fri, 12 May 2023 20:02:23 +0000 [thread overview] Message-ID: <bug-109829-4-HjgoNRsVdz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109829-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109829 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Don't you need also (simplify (cond (eq (SIGNBIT @0) zero_p@1) (neg @0) @0) (neg (abs @0))) (simplify (cond (eq (SIGNBIT @0) zero_p@1) @0 (neg @0)) (abs @0)) ? Or does match.pd try to invert all the COND_EXPR conditions and swap the operands?
next prev parent reply other threads:[~2023-05-12 20:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-12 13:23 [Bug tree-optimization/109829] New: " antoshkka at gmail dot com 2023-05-12 18:16 ` [Bug tree-optimization/109829] " pinskia at gcc dot gnu.org 2023-05-12 19:25 ` pinskia at gcc dot gnu.org 2023-05-12 19:34 ` pinskia at gcc dot gnu.org 2023-05-12 20:02 ` jakub at gcc dot gnu.org [this message] 2023-05-12 20:03 ` jakub at gcc dot gnu.org 2023-05-12 20:18 ` pinskia at gcc dot gnu.org 2023-05-13 15:53 ` pinskia at gcc dot gnu.org 2023-05-13 22:29 ` pinskia at gcc dot gnu.org 2023-05-14 4:04 ` pinskia at gcc dot gnu.org 2023-05-14 23:08 ` cvs-commit at gcc dot gnu.org 2023-05-14 23:09 ` 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-109829-4-HjgoNRsVdz@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).