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/107394] [13 Regression] ICE in verify_range, at value-range.cc:716 since r13-3411-gf4fda3eec408e1eb Date: Thu, 27 Oct 2022 09:40:51 +0000 [thread overview] Message-ID: <bug-107394-4-fmv1vfi2MR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107394-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107394 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>: https://gcc.gnu.org/g:2b1fb720818a85d5c893ce65d140add40debf2ff commit r13-3525-g2b1fb720818a85d5c893ce65d140add40debf2ff Author: Aldy Hernandez <aldyh@redhat.com> Date: Tue Oct 25 22:44:51 2022 +0200 [PR tree-optimization/107394] Canonicalize global franges as they are read back. The problem here is that we're inlining a global range with NANs into a function that has been tagged with __attribute__((optimize ("-ffinite-math-only"))). As the global range is copied from SSA_NAME_RANGE_INFO, its NAN bits are copied, which then cause frange::verify_range() to fail a sanity check making sure no NANs creep in when !HONOR_NANS. I think what we should do is nuke the NAN bits as we're restoring the global range. For that matter, if we use the frange constructor, everything except that NAN sign will be done automatically, including dropping INFs to the min/max representable range when appropriate. PR tree-optimization/107394 gcc/ChangeLog: * value-range-storage.cc (frange_storage_slot::get_frange): Use frange constructor. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/pr107394.c: New test.
next prev parent reply other threads:[~2022-10-27 9:40 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-25 15:30 [Bug tree-optimization/107394] New: [13 Regression] ICE in verify_range, at value-range.cc:716 asolokha at gmx dot com 2022-10-25 16:49 ` [Bug tree-optimization/107394] " pinskia at gcc dot gnu.org 2022-10-25 19:29 ` [Bug tree-optimization/107394] [13 Regression] ICE in verify_range, at value-range.cc:716 since r13-3411-gf4fda3eec408e1eb marxin at gcc dot gnu.org 2022-10-25 20:47 ` aldyh at gcc dot gnu.org 2022-10-25 20:47 ` aldyh at gcc dot gnu.org 2022-10-25 20:48 ` aldyh at gcc dot gnu.org 2022-10-27 9:40 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-27 9:41 ` aldyh 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-107394-4-fmv1vfi2MR@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).