public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tlange at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/106551] [13 Regression] dup2 causes -fanalyzer ICE in valid_to_unchecked_state, at analyzer/sm-fd.cc:751
Date: Sun, 14 Aug 2022 20:27:02 +0000 [thread overview]
Message-ID: <bug-106551-4-5j8uwwJmfc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106551-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106551
Tim Lange <tlange at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tlange at gcc dot gnu.org
--- Comment #4 from Tim Lange <tlange at gcc dot gnu.org> ---
Hi Immad,
while testing my patch on coreutils [1], I encountered another ICE at the same
line. I'm using the newest commit on the master at the time of writing this [2]
(I've double-checked that I indeed have your fix included).
during IPA pass: analyzer
../lib/freopen.c: In function 'rpl_freopen':
../lib/freopen.c:82:19: internal compiler error: in valid_to_unchecked_state,
at analyzer/sm-fd.cc:751
82 | if (dup2 (nullfd, fd) < 0)
| ^~~~~~~~~~~~~~~~~
0x7bc106 valid_to_unchecked_state
../../gcc/analyzer/sm-fd.cc:751
0x7bc106 valid_to_unchecked_state
../../gcc/analyzer/sm-fd.cc:742
0x7bc106 check_for_dup
../../gcc/analyzer/sm-fd.cc:990
0x12a5e8c on_stmt
../../gcc/analyzer/sm-fd.cc:805
0x124f4e4 ana::exploded_node::on_stmt(ana::exploded_graph&, ana::supernode
const*, gimple const*, ana::program_state*, ana::uncertainty_t*,
ana::path_context*)
../../gcc/analyzer/engine.cc:1449
0x1251f1b ana::exploded_graph::process_node(ana::exploded_node*)
../../gcc/analyzer/engine.cc:3868
0x1252dba ana::exploded_graph::process_worklist()
../../gcc/analyzer/engine.cc:3271
0x125514d ana::impl_run_checkers(ana::logger*)
../../gcc/analyzer/engine.cc:5912
0x125614e ana::run_checkers()
../../gcc/analyzer/engine.cc:5986
0x1245ee8 execute
../../gcc/analyzer/analyzer-pass.cc:87
[1] compiling coreutils commit:
https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commit;h=9f71f478ec6929d323c17f0482db8791de87b4fd
[2]
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=fe4dc4f553d8639b0ce3465e5e6dcf61c1ae9752
next prev parent reply other threads:[~2022-08-14 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 6:39 [Bug analyzer/106551] New: [13 Regression] dup2 causes -fanalyser " slyfox at gcc dot gnu.org
2022-08-08 6:52 ` [Bug analyzer/106551] " rguenth at gcc dot gnu.org
2022-08-08 14:02 ` dmalcolm at gcc dot gnu.org
2022-08-09 7:48 ` [Bug analyzer/106551] [13 Regression] dup2 causes -fanalyzer " mir at gcc dot gnu.org
2022-08-11 16:21 ` cvs-commit at gcc dot gnu.org
2022-08-14 20:27 ` tlange at gcc dot gnu.org [this message]
2022-08-15 8:37 ` mir at gcc dot gnu.org
2022-08-15 16:52 ` cvs-commit at gcc dot gnu.org
2022-08-15 16:55 ` mir 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-106551-4-5j8uwwJmfc@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).