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/107547] [13 Regression] ICE in get_no_error_domain, at tree-call-cdce.cc:769 since r13-3568-g7f940822816917fe
Date: Tue, 08 Nov 2022 12:24:56 +0000	[thread overview]
Message-ID: <bug-107547-4-Ns505EDR3r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107547-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107547

--- Comment #2 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:970dcd567449ec510477a043bbff70a0b960bd7f

commit r13-3804-g970dcd567449ec510477a043bbff70a0b960bd7f
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Nov 8 13:24:02 2022 +0100

    cdce: Fix up get_no_error_domain for new f{16,32,64,128} builtins
[PR107547]

    I've missed that this function needs to handle all the builtins that
    are handled in can_test_argument_range.
    The following patch does that.  For many of the builtins (like acos, or
    log) it is the same range regardless of the floating point type, but for
    some (cosh, sinh, exp{,m1,2}) it is different for each format,
    so I had to compute those ranges.

    Note, seems the existing ranges were in some cases (e.g. for exp2)
    the smallest in absolute value which results infinite result, in others
    the largest which still results in finite result (but consistently so
    for the IEEE single vs. double).  I've followed that for IEEE half and
    quad cases too, just am not sure why it was like that.  I think
    get_domain with true, false is open interval rather than closed
    and the comments indicate that too, conservatively that is certainly
    correct.

    OT, with frange, perhaps we could DCE the calls unconditionally if
    frange can prove we are in the domain range.

    2022-11-08  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/107547
            * tree-call-cdce.cc (get_no_error_domain): Handle
CASE_FLT_FN_FLOATN_NX
            of BUILT_IN_{ACOS,ASIN,ACOSH,ATANH,LOG,LOG2,LOG10,LOG1P}.  Handle
            BUILT_IN_{COSH,SINH,EXP,EXPM1,EXP2}F{16,32,64,128}.

            * gcc.dg/pr107547.c: New test.

  parent reply	other threads:[~2022-11-08 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  9:16 [Bug tree-optimization/107547] New: " marxin at gcc dot gnu.org
2022-11-07  9:16 ` [Bug tree-optimization/107547] " marxin at gcc dot gnu.org
2022-11-07 14:06 ` jakub at gcc dot gnu.org
2022-11-08 12:24 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-08 12:25 ` [Bug tree-optimization/107547] [13 Regression] " 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-107547-4-Ns505EDR3r@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: link
Be 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).