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 testsuite/98575] New: [11 regression] gcc.dg/analyzer/pr94851-1.c fails after r11-6495
Date: Wed, 06 Jan 2021 19:54:33 +0000 [thread overview]
Message-ID: <bug-98575-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98575
Bug ID: 98575
Summary: [11 regression] gcc.dg/analyzer/pr94851-1.c fails
after r11-6495
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:df1eba3ceada6e8990c00ccfa6c5a2c9b1c13334, r11-6495
The revision claims the message went away but I am still seeing it.
make -k check-gcc RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/pr94851-1.c"
FAIL: gcc.dg/analyzer/pr94851-1.c bogus leak (test for bogus messages, line 43)
# of expected passes 1
# of unexpected failures 1
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/pr94851-1.c
-fdiagnostics-plain-output -fanalyzer -Wanalyzer-too-complex
-fanalyzer-call-summaries -O2 -S -o pr94851-1.s
In function 'pamark':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:43:13:
warning: leak of 'p' [CWE-401] [-Wanalyzer-malloc-leak]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:24:29:
note: (1) following 'false' branch (when 'p' is NULL)...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:29:6:
note: (2) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:29:6:
note: (3) following 'false' branch (when 'p' is NULL)...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:32:23:
note: (4) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:32:23:
note: (5) allocated here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:32:8:
note: (6) assuming 'p' is non-NULL
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:32:8:
note: (7) following 'false' branch (when 'p' is non-NULL)...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:35:15:
note: (8) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:37:8:
note: (9) following 'true' branch...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:38:22:
note: (10) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr94851-1.c:43:13:
note: (11) 'p' leaks here; was allocated at (5)
FAIL: gcc.dg/analyzer/pr94851-1.c bogus leak (test for bogus messages, line 43)
Executing on host: /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled44120.cc
-fdiagnostics-plain-output -S -o exceptions_enabled44120.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_enabled44120.cc
-fdiagnostics-plain-output -S -o exceptions_enabled44120.s
PASS: gcc.dg/analyzer/pr94851-1.c (test for excess errors)
testcase
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/analyzer.exp
completed in 0 seconds
=== gcc Summary ===
# of expected passes 1
# of unexpected failures 1
next reply other threads:[~2021-01-06 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 19:54 seurer at gcc dot gnu.org [this message]
2021-01-07 8:27 ` [Bug analyzer/98575] " rguenth at gcc dot gnu.org
2021-02-04 19:38 ` dmalcolm at gcc dot gnu.org
2021-02-04 23:02 ` dmalcolm at gcc dot gnu.org
2021-02-04 23:16 ` dmalcolm at gcc dot gnu.org
2021-02-04 23:48 ` dmalcolm at gcc dot gnu.org
2021-02-09 20:53 ` [Bug analyzer/98575] [11 regression] False -Wanalyzer-malloc-leak on code path involving unknown function call cvs-commit at gcc dot gnu.org
2021-02-09 20:55 ` cvs-commit at gcc dot gnu.org
2021-02-09 21:05 ` 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-98575-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).