public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107972] New: backward propagation of finite property not performed Date: Mon, 05 Dec 2022 13:35:28 +0000 [thread overview] Message-ID: <bug-107972-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107972 Bug ID: 107972 Summary: backward propagation of finite property not performed Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: drepper.fsp+rhbz at gmail dot com Target Milestone: --- Here is another example where with the help of the FP ranger capabilities the compiler should generate better code than it does today (trunk): double f(double a, double b) { if (!__builtin_isfinite(a)) return -1.0; double res = a + b; if (! __builtin_isfinite(res)) __builtin_unreachable(); return res; } The condition guaranteed by the __builtin_unreachable implies that neither a nor b cannot be finite. Hence the initial comparison can be elided. The same is true for - and * and also for the first operand of /.
next reply other threads:[~2022-12-05 13:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-05 13:35 drepper.fsp+rhbz at gmail dot com [this message] 2022-12-05 13:43 ` [Bug tree-optimization/107972] " jakub at gcc dot gnu.org 2022-12-06 9:27 ` cvs-commit at gcc dot gnu.org 2022-12-06 9:57 ` jakub at gcc dot gnu.org 2022-12-07 15:31 ` amacleod at redhat dot com 2023-02-14 21:28 ` amacleod at redhat 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-107972-4@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).