public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/107396] New: [12 regression] new test case gcc.dg/analyzer/pipe-glibc.c in r13-3466-g792f039fc37faa fails with excess errors
@ 2022-10-25 17:00 seurer at gcc dot gnu.org
  2022-10-27 23:23 ` [Bug analyzer/107396] [13 " pinskia at gcc dot gnu.org
                   ` (9 more replies)
  0 siblings, 10 replies; 11+ messages in thread
From: seurer at gcc dot gnu.org @ 2022-10-25 17:00 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107396

            Bug ID: 107396
           Summary: [12 regression] new test case
                    gcc.dg/analyzer/pipe-glibc.c in
                    r13-3466-g792f039fc37faa fails with excess errors
           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:792f039fc37faa3446725a643c8018f084e8ccab, r13-3466-g792f039fc37faa
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


I am only seeing this failure on power 9.  It works fine on power 8 and power
10.


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]

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
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]

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2023-03-31 20:54 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-25 17:00 [Bug target/107396] New: [12 regression] new test case gcc.dg/analyzer/pipe-glibc.c in r13-3466-g792f039fc37faa fails with excess errors seurer at gcc dot gnu.org
2022-10-27 23:23 ` [Bug analyzer/107396] [13 " pinskia at gcc dot gnu.org
2022-10-28 11:12 ` rguenth at gcc dot gnu.org
2022-12-02 10:13 ` marxin at gcc dot gnu.org
2023-01-13 11:35 ` rguenth at gcc dot gnu.org
2023-02-14  8:27 ` linkw at gcc dot gnu.org
2023-03-15  9:47 ` rguenth at gcc dot gnu.org
2023-03-15 14:33 ` dave.anglin at bell dot net
2023-03-29 17:16 ` jakub at gcc dot gnu.org
2023-03-31 20:49 ` cvs-commit at gcc dot gnu.org
2023-03-31 20:54 ` jakub at gcc dot gnu.org

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).