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/107446] New: New test case gcc.dg/analyzer/pipe-glibc.c in r13-3466-g792f039fc37faa has excess errors Date: Thu, 27 Oct 2022 23:19:09 +0000 [thread overview] Message-ID: <bug-107446-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107446 Bug ID: 107446 Summary: New test case gcc.dg/analyzer/pipe-glibc.c in r13-3466-g792f039fc37faa has excess errors Product: gcc Version: 13.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:792f039fc37faa3446725a643c8018f084e8ccab, r13-3466-g792f039fc37faa I only saw this on a power 9. It ran OK on power 8 and power 10 machines. configure --enable-languages=c,fortran,c++ --with-cpu=power9 --disable-bootstrap --disable-multilib make -k check-gcc RUNTESTFLAGS="analyzer.exp=gcc.dg/analyzer/pipe-glibc.c" FAIL: gcc.dg/analyzer/pipe-glibc.c (test for excess errors) # 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/pipe-glibc.c -fdiagnostics-plain-output -fanalyzer -Wanalyzer-too-complex -fanalyzer-call-summaries -S -o pipe-glibc.s^M /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c: In function 'write_to_pipe':^M /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c:28:3: warning: use of possibly-NULL 'stream' where non-null expected [CWE-690] [-Wanalyzer-possible-null-argument]^M /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c:27:12: note: (1) this call could return NULL^M /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c:28:3: note: (2) argument 4 ('stream') from (1) could be NULL where non-null expected^M <built-in>: note: argument 4 of '__builtin_fwrite' must be non-null^M Executing on host: /home/seurer/gcc/git/build/gcc-test/gcc/xgcc -B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled106355.cc -fdiagnostics-plain-output -S -o exceptions_enabled106355.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_enabled106355.cc -fdiagnostics-plain-output -S -o exceptions_enabled106355.s^M FAIL: gcc.dg/analyzer/pipe-glibc.c (test for excess errors) Excess errors: /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pipe-glibc.c:28:3: warning: use of possibly-NULL 'stream' where non-null expected [CWE-690] [-Wanalyzer-possible-null-argument] commit 792f039fc37faa3446725a643c8018f084e8ccab (HEAD, refs/bisect/bad) Author: David Malcolm <dmalcolm@redhat.com> Date: Mon Oct 24 16:38:22 2022 -0400 analyzer: handle "pipe" and "pipe2" [PR106300]
next reply other threads:[~2022-10-27 23:19 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-27 23:19 seurer at gcc dot gnu.org [this message] 2022-10-27 23:23 ` [Bug testsuite/107446] " pinskia at gcc dot gnu.org 2022-10-27 23:41 ` 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-107446-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: linkBe 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).