public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/96798] New: Analyzer failures on Darwin
Date: Wed, 26 Aug 2020 12:48:00 +0000 [thread overview]
Message-ID: <bug-96798-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
Bug ID: 96798
Summary: Analyzer failures on Darwin
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: dominiq at lps dot ens.fr
CC: iains at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-apple-darwin19.6
Target: x86_64-apple-darwin19.6
Build: x86_64-apple-darwin19.6
On Darwin I get the following failures
FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 519)
FAIL: gcc.dg/analyzer/data-model-1.c (test for warnings, line 520)
FAIL: gcc.dg/analyzer/data-model-1.c (test for excess errors)
FAIL: gcc.dg/analyzer/memset-1.c (test for warnings, line 67)
FAIL: gcc.dg/analyzer/memset-1.c (test for warnings, line 68)
FAIL: gcc.dg/analyzer/memset-1.c (test for excess errors)
due to
/opt/gcc/work/gcc/testsuite/gcc.dg/analyzer/data-model-1.c: In function
'test_27':
/opt/gcc/work/gcc/testsuite/gcc.dg/analyzer/data-model-1.c:519:3: warning:
UNKNOWN
519 | __analyzer_eval (p->x == 0); /* { dg-warning "TRUE" } */
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/gcc/work/gcc/testsuite/gcc.dg/analyzer/data-model-1.c:520:3: warning:
UNKNOWN
520 | __analyzer_eval (p->y == 0); /* { dg-warning "TRUE" } */
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
and
/opt/gcc/work/gcc/testsuite/gcc.dg/analyzer/memset-1.c:67:3: warning: TRUE
67 | __analyzer_eval (buf[42] == 'A'); /* { dg-warning "UNKNOWN" } */
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/gcc/work/gcc/testsuite/gcc.dg/analyzer/memset-1.c:68:3: warning: FALSE
68 | __analyzer_eval (buf[42] == '\0'); /* { dg-warning "UNKNOWN" } */
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2020-08-26 12:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 12:48 dominiq at lps dot ens.fr [this message]
2020-08-27 22:49 ` [Bug analyzer/96798] " dmalcolm at gcc dot gnu.org
2020-08-27 23:30 ` dominiq at lps dot ens.fr
2020-08-28 10:10 ` dmalcolm at gcc dot gnu.org
2020-08-28 11:20 ` dominiq at lps dot ens.fr
2020-08-28 22:39 ` dominiq at lps dot ens.fr
2020-08-29 0:58 ` dmalcolm at gcc dot gnu.org
2020-08-29 7:02 ` iains at gcc dot gnu.org
2020-08-29 7:21 ` iains at gcc dot gnu.org
2020-08-29 7:22 ` iains at gcc dot gnu.org
2020-08-31 22:31 ` cvs-commit at gcc dot gnu.org
2020-08-31 22:32 ` cvs-commit at gcc dot gnu.org
2020-08-31 22:47 ` dmalcolm at gcc dot gnu.org
2020-09-11 1:09 ` cvs-commit at gcc dot gnu.org
2020-09-11 1:13 ` 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-96798-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).