public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/97621] New: [11 regression] bogus message in gcc.dg/analyzer/malloc-vs-local-1b.c after r11-4434
Date: Wed, 28 Oct 2020 18:49:36 +0000 [thread overview]
Message-ID: <bug-97621-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97621
Bug ID: 97621
Summary: [11 regression] bogus message in
gcc.dg/analyzer/malloc-vs-local-1b.c after r11-4434
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:b0702ac5588333e27d7ec43d21d704521f7a05c6, r11-4434
make -k check-gcc
RUNTESTFLAGS=analyzer.exp=gcc.dg/analyzer/malloc-vs-local-1b.c
FAIL: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 170)
# of expected passes 22
# of unexpected failures 1
commit b0702ac5588333e27d7ec43d21d704521f7a05c6
Author: David Malcolm <dmalcolm@redhat.com>
Date: Tue Oct 27 09:51:19 2020 -0400
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c
-fdiagnostics-plain-output -fanalyzer -Wanalyzer-too-complex
-fanalyzer-call-summaries -fanalyzer-call-summaries -S -o malloc-vs-local-1b.s
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:
In function 'test_initial_flag':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:170:5:
warning: 'free' of 'ptr' which points to memory not on the heap [CWE-590]
[-Wanalyzer-free-of-non-heap]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:158:6:
note: (1) following 'false' branch (when 'on_heap == 0')...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:161:9:
note: (2) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:161:9:
note: (3) pointer is from here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:169:6:
note: (4) following 'true' branch (when 'n > 10')...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:170:5:
note: (5) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:170:5:
note: (6) call to 'free' here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:
At top level:
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:47:3:
warning: 2 processed enodes: [EN: 69-70]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:51:3:
warning: 2 processed enodes: [EN: 75-76]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:72:3:
warning: 2 processed enodes: [EN: 105-106]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:101:3:
warning: 2 processed enodes: [EN: 125-126]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:105:3:
warning: 2 processed enodes: [EN: 131-132]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:126:3:
warning: 2 processed enodes: [EN: 161-162]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:130:3:
warning: 2 processed enodes: [EN: 167-168]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:156:3:
warning: 1 processed enode: [EN: 196]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:163:3:
warning: 2 processed enodes: [EN: 207-208]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:167:3:
warning: 2 processed enodes: [EN: 213-214]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/malloc-vs-local-1b.c:76:3:
warning: 2 processed enodes: [EN: 263, EN: 275]
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 16)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 47)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 51)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 54)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 56)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 72)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 76)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 79)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 81)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 101)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 105)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 108)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 110)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 126)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 130)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 133)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 135)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 156)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 163)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for warnings, line 167)
FAIL: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 170)
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for bogus messages, line 172)
Executing on host: /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled69408.cc
-fdiagnostics-plain-output -S -o exceptions_enabled69408.s (timeout = 300)
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled69408.cc
-fdiagnostics-plain-output -S -o exceptions_enabled69408.s
PASS: gcc.dg/analyzer/malloc-vs-local-1b.c (test for excess errors)
testcase
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/analyzer.exp
completed in 0 seconds
next reply other threads:[~2020-10-28 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 18:49 seurer at gcc dot gnu.org [this message]
2020-10-28 19:57 ` [Bug analyzer/97621] " 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-97621-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).