public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/107072] New: Analyzer call summarization not taking into account side-effects of calls
Date: Wed, 28 Sep 2022 15:57:32 +0000 [thread overview]
Message-ID: <bug-107072-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107072
Bug ID: 107072
Summary: Analyzer call summarization not taking into account
side-effects of calls
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: dmalcolm at gcc dot gnu.org
Blocks: 99390, 107060
Target Milestone: ---
Created attachment 53637
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53637&action=edit
Reproducer reduced from PR 107060
-fanalyzer-call-summaries doesn't seem to be taking account of the side-effects
of calls; it emit lots of -Wanalyzer-use-of-uninitialized-value false positives
on the reproducer for PR 107060.
Am attaching a minimized version, which emits these false positives:
$ ./xgcc -B. -S -fanalyzer ../../src/uninit.c -fanalyzer-call-summaries
../../src/uninit.c: In function ‘fetch_string_char_advance’:
../../src/uninit.c:52:7: warning: use of uninitialized value ‘chlen’ [CWE-457]
[-Wanalyzer-use-of-uninitialized-value]
52 | b += chlen;
| ^~
‘fetch_string_char_advance’: events 1-5
|
| 49 | if (STRING_MULTIBYTE(string)) {
| | ~
| | |
| | (3) following ‘true’ branch...
| 50 | int chlen;
| | ^~~~~
| | |
| | (1) region created on stack here
| | (2) capacity: 4 bytes
| 51 | output = string_char_and_length(chp, &chlen);
| | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| | |
| | (4) ...to here
| 52 | b += chlen;
| | ~~
| | |
| | (5) use of uninitialized value ‘chlen’ here
|
../../src/uninit.c: In function ‘fetch_string_char_as_multibyte_advance’:
../../src/uninit.c:70:7: warning: use of uninitialized value ‘chlen’ [CWE-457]
[-Wanalyzer-use-of-uninitialized-value]
70 | b += chlen;
| ^~
‘fetch_string_char_as_multibyte_advance’: events 1-5
|
| 67 | if (STRING_MULTIBYTE(string)) {
| | ~
| | |
| | (3) following ‘true’ branch...
| 68 | int chlen;
| | ^~~~~
| | |
| | (1) region created on stack here
| | (2) capacity: 4 bytes
| 69 | output = string_char_and_length(chp, &chlen);
| | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| | |
| | (4) ...to here
| 70 | b += chlen;
| | ~~
| | |
| | (5) use of uninitialized value ‘chlen’ here
|
...despite string_char_and_length writing back to chlen (aka *length) on every
possible outcome.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99390
[Bug 99390] [meta-bug] tracker bug for call summaries in -fanalyzer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107060
[Bug 107060] -fanalyzer unbearably slow when compiling GNU Emacs
next reply other threads:[~2022-09-28 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 15:57 dmalcolm at gcc dot gnu.org [this message]
2022-10-05 0:20 ` [Bug analyzer/107072] " cvs-commit at gcc dot gnu.org
2022-10-05 0:27 ` 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-107072-4@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).