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 target/108722] New: gcc.dg/analyzer/file-CWE-1341-example.c fails on power 9 BE
Date: Wed, 08 Feb 2023 17:46:16 +0000 [thread overview]
Message-ID: <bug-108722-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108722
Bug ID: 108722
Summary: gcc.dg/analyzer/file-CWE-1341-example.c fails on power
9 BE
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:9ada45967b4cf543aa47091e99a760d0718013cc, r13-4218-g9ada45967b4cf5
This is only failing on a power 9 BE machine. It fails since the test case's
introduction.
make -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32}'
analyzer.exp=gcc.dg/analyzer/file-CWE-1341-example.c"
FAIL: gcc.dg/analyzer/file-CWE-1341-example.c (test for excess errors)
# of expected passes 3
# 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/file-CWE-1341-example.c
-m32 -fdiagnostics-plain-output -fanalyzer -Wanalyzer-too-complex
-fanalyzer-call-summaries -S -o file-CWE-1341-example.s
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:
In function 'example_1':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:38:16:
warning: double 'fclose' of FILE 'f' [CWE-1341] [-Wanalyzer-double-fclose]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:29:13:
note: (1) opened here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:30:6:
note: (2) assuming 'f' is non-NULL
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:30:6:
note: (3) following 'true' branch (when 'f' is non-NULL)...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:32:12:
note: (4) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:35:16:
note: (5) first 'fclose' here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:38:16:
note: (6) second 'fclose' here; first 'fclose' was at (5)
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:38:16:
warning: double-'fclose' of 'f' [CWE-415] [-Wanalyzer-double-free]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:29:13:
note: (1) allocated here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:30:6:
note: (2) assuming 'f' is non-NULL
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:30:6:
note: (3) following 'true' branch (when 'f' is non-NULL)...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:32:12:
note: (4) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:35:16:
note: (5) first 'fclose' here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:38:16:
note: (6) second 'fclose' here; first 'fclose' was at (5)
PASS: gcc.dg/analyzer/file-CWE-1341-example.c (test for warnings, line 29)
PASS: gcc.dg/analyzer/file-CWE-1341-example.c (test for warnings, line 35)
PASS: gcc.dg/analyzer/file-CWE-1341-example.c (test for warnings, line 38)
Executing on host: /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled4193687.cc -m32
-fdiagnostics-plain-output -S -o exceptions_enabled4193687.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_enabled4193687.cc -m32
-fdiagnostics-plain-output -S -o exceptions_enabled4193687.s
FAIL: gcc.dg/analyzer/file-CWE-1341-example.c (test for excess errors)
Excess errors:
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/file-CWE-1341-example.c:38:16:
warning: double-'fclose' of 'f' [CWE-415] [-Wanalyzer-double-free]
next reply other threads:[~2023-02-08 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 17:46 seurer at gcc dot gnu.org [this message]
2023-04-02 15:04 ` [Bug target/108722] " danglin at gcc dot gnu.org
2023-04-11 9:23 ` guojiufu at gcc dot gnu.org
2023-04-13 7:38 ` [Bug analyzer/108722] " rguenth at gcc dot gnu.org
2023-04-14 3:10 ` cvs-commit at gcc dot gnu.org
2024-03-04 13:00 ` [Bug analyzer/108722] [13/14 Regression] " rguenth at gcc dot gnu.org
2024-03-08 15:39 ` law at gcc dot gnu.org
2024-03-08 22:17 ` seurer 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-108722-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).