public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107591] range-op{,-float}.cc for x * x Date: Sat, 12 Nov 2022 08:42:52 +0000 [thread overview] Message-ID: <bug-107591-4-vD2n6x35zK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107591-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107591 --- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:2f7f9edd28d75a85a33599978f23811e679e443d commit r13-3923-g2f7f9edd28d75a85a33599978f23811e679e443d Author: Jakub Jelinek <jakub@redhat.com> Date: Sat Nov 12 09:33:01 2022 +0100 range-op: Implement floating point multiplication fold_range [PR107569] The following patch implements frange multiplication, including the special case of x * x. The callers don't tell us that it is x * x, just that it is either z = x * x or if (x == y) z = x * y; For irange that makes no difference, but for frange it can mean x is -0.0 and y is 0.0 if they have the same range that includes both signed and unsigned zeros, so we need to assume result could be -0.0. The patch causes one regression: +FAIL: gcc.dg/fold-overflow-1.c scan-assembler-times 2139095040 2 but that is already tracked in PR107608 and affects not just the newly added multiplication, but addition and other floating point operations (and doesn't seem like a ranger bug but dce or whatever else). 2022-11-12 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/107569 PR tree-optimization/107591 * range-op.h (range_operator_float::rv_fold): Add relation_kind argument. * range-op-float.cc (range_operator_float::fold_range): Name last argument trio and pass trio.op1_op2 () as last argument to rv_fold. (range_operator_float::rv_fold): Add relation_kind argument. (foperator_plus::rv_fold, foperator_minus::rv_fold): Likewise. (foperator_mult): New class. (floating_op_table::floating_op_table): Use foperator_mult for MULT_EXPR.
next prev parent reply other threads:[~2022-11-12 8:42 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-09 15:37 [Bug tree-optimization/107591] New: " jakub at gcc dot gnu.org 2022-11-09 15:49 ` [Bug tree-optimization/107591] " aldyh at gcc dot gnu.org 2022-11-09 15:55 ` aldyh at gcc dot gnu.org 2022-11-09 15:57 ` jakub at gcc dot gnu.org 2022-11-09 15:59 ` pinskia at gcc dot gnu.org 2022-11-09 16:01 ` pinskia at gcc dot gnu.org 2022-11-09 16:02 ` aldyh at gcc dot gnu.org 2022-11-09 16:04 ` aldyh at gcc dot gnu.org 2022-11-09 16:31 ` jakub at gcc dot gnu.org 2022-11-09 16:40 ` jakub at gcc dot gnu.org 2022-11-09 17:45 ` amacleod at redhat dot com 2022-11-09 17:49 ` jakub at gcc dot gnu.org 2022-11-09 18:22 ` amacleod at redhat dot com 2022-11-09 18:35 ` jakub at gcc dot gnu.org 2022-11-09 19:20 ` amacleod at redhat dot com 2022-11-09 20:24 ` jakub at gcc dot gnu.org 2022-11-09 20:45 ` jakub at gcc dot gnu.org 2022-11-09 22:25 ` amacleod at redhat dot com 2022-11-09 23:27 ` jakub at gcc dot gnu.org 2022-11-12 8:42 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-05 7:14 ` pilarlatiesa 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-107591-4-vD2n6x35zK@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).