public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/95008] New: [11 regression] excess errors in gcc.dg/analyzer/pr93382.c and gcc.dg/two-types-6.c after r11-169
Date: Fri, 08 May 2020 14:19:50 +0000 [thread overview]
Message-ID: <bug-95008-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95008
Bug ID: 95008
Summary: [11 regression] excess errors in
gcc.dg/analyzer/pr93382.c and gcc.dg/two-types-6.c
after r11-169
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at linux dot vnet.ibm.com
Target Milestone: ---
this run : g:f8a4141bae53f9125d374e5873dcda3f75392f1f, r11-169
FAIL: gcc.dg/analyzer/pr93382.c (test for warnings, line 17)
FAIL: gcc.dg/two-types-6.c (test for warnings, line 5)
The changes in r11-169 cause these tests to now fail, at least on powerpc64.
Executing on host: /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/pr93382.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -fanalyzer
-fdiagnostics-path-format=separate-events -Wanalyzer-too-complex
-fanalyzer-call-summaries -fanalyzer-checker=taint -S -o pr93382.s (timeout
= 300)
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/pr93382.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -fanalyzer
-fdiagnostics-path-format=separate-events -Wanalyzer-too-complex
-fanalyzer-call-summaries -fanalyzer-checker=taint -S -o pr93382.s
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93382.c: In
function 'pl':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93382.c:26:13:
warning: use of tainted value 'idx' in array lookup without bounds checking
[CWE-129] [-Wanalyzer-tainted-array-index]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93382.c:23:1:
note: (1) entry to 'pl'
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93382.c:25:3:
note: (2) calling 'ql' from 'pl'
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93382.c:12:1:
note: (3) entry to 'ql'
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93382.c:16:3:
note: (4) 'n1' gets an unchecked value here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93382.c:17:7:
note: (5) 'idx' has an unchecked value here (from 'n1')
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93382.c:25:3:
note: (6) returning to 'pl' from 'ql'
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93382.c:26:13:
note: (7) use of tainted value 'idx' in array lookup without bounds checking
PASS: gcc.dg/analyzer/pr93382.c (test for warnings, line 16)
FAIL: gcc.dg/analyzer/pr93382.c (test for warnings, line 17)
PASS: gcc.dg/analyzer/pr93382.c (test for warnings, line 26)
PASS: gcc.dg/analyzer/pr93382.c (test for excess errors)
Executing on host: /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/two-types-6.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -std=gnu89 -S -o
two-types-6.s (timeout = 300)
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/two-types-6.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -std=gnu89 -S -o
two-types-6.s
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/two-types-6.c:6:3: error:
expected ';', identifier or '(' before 'struct'
compiler exited with status 1
FAIL: gcc.dg/two-types-6.c (test for warnings, line 5)
PASS: gcc.dg/two-types-6.c (test for errors, line 6)
PASS: gcc.dg/two-types-6.c (test for excess errors)
next reply other threads:[~2020-05-08 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 14:19 seurer at linux dot vnet.ibm.com [this message]
2020-05-08 16:22 ` [Bug testsuite/95008] " hjl.tools at gmail dot com
2020-05-08 21:30 ` ro at gcc dot gnu.org
2020-05-08 23:00 ` manfred99 at gmx dot ch
2020-05-09 18:29 ` cvs-commit at gcc dot gnu.org
2020-05-09 18:31 ` jakub 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-95008-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).