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 analyzer/107210] [13 Regression] ICE in tree_to_uhwi, at tree.cc:6392 since r13-3168-gf09b99550a3c6cd1
Date: Thu, 13 Oct 2022 20:06:27 +0000 [thread overview]
Message-ID: <bug-107210-4-W3L69TFP8o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107210-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107210
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:99da523359e9333555585484eb3b8f854a98f1b4
commit r13-3285-g99da523359e9333555585484eb3b8f854a98f1b4
Author: David Malcolm <dmalcolm@redhat.com>
Date: Thu Oct 13 16:05:35 2022 -0400
analyzer: fix ICE introduced in r13-3168 [PR107210]
gcc/analyzer/ChangeLog:
PR analyzer/107210
* svalue.cc (constant_svalue::maybe_fold_bits_within): Only
attempt to extract individual bits when tree_fits_uhwi_p.
gcc/testsuite/ChangeLog:
PR analyzer/107210
* gfortran.dg/analyzer/pr107210.f90: New test.
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-10-13 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 4:39 [Bug analyzer/107210] New: [13 Regression] ICE in tree_to_uhwi, at tree.cc:6392 asolokha at gmx dot com
2022-10-11 7:23 ` [Bug analyzer/107210] [13 Regression] ICE in tree_to_uhwi, at tree.cc:6392 since r13-3168-gf09b99550a3c6cd1 marxin at gcc dot gnu.org
2022-10-11 7:27 ` rguenth at gcc dot gnu.org
2022-10-13 20:06 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-13 20:11 ` dmalcolm 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-107210-4-W3L69TFP8o@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).