[Bug testsuite/96609] New: new test case gcc.dg/analyzer/init.c has many failures

public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed

* [Bug testsuite/96609] New: new test case gcc.dg/analyzer/init.c has many failures
@ 2020-08-13 23:02 seurer at gcc dot gnu.org
  2020-08-14  4:40 ` [Bug testsuite/96609] " seurer at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: seurer at gcc dot gnu.org @ 2020-08-13 23:02 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 96609
           Summary: new test case gcc.dg/analyzer/init.c has many failures
           Product: gcc
           Version: 11.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:808f4dfeb3a95f50f15e71148e5c1067f90a126d, r11-2694

make -k check-gcc RUNTESTFLAGS=analyzer.exp=gcc.dg/analyzer/init.c

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/init.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 -S -o init.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/init.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 -S -o init.s
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_1':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:30:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:31:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_2':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:37:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:38:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_3':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:44:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:45:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_4':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:51:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:52:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_5':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:58:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:59:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_6':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:65:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:66:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_7':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:72:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:73:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:74:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:75:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_8':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:81:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:82:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:83:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:84:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_9':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:90:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:91:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:92:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:93:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_10':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:99:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:100:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:101:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:102:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_11':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:108:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:109:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:110:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:111:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_12':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:117:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:118:3:
warning: TRUE
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_13':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:124:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:125:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:126:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:127:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:128:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:129:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c: In function
'test_14':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:135:3:
warning: TRUE
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 30)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 31)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 37)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 38)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 44)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 45)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 51)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 52)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 58)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 59)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 65)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 66)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 72)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 73)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 74)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 75)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 81)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 82)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 83)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 84)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 90)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 91)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 92)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 93)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 99)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 100)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 101)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 102)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 108)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 109)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 110)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 111)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 117)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 118)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 124)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 125)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 126)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 127)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 128)
FAIL: gcc.dg/analyzer/init.c  (test for warnings, line 129)
PASS: gcc.dg/analyzer/init.c  (test for warnings, line 135)
FAIL: gcc.dg/analyzer/init.c (test for excess errors)
Excess errors:
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:72:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:73:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:74:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:75:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:99:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:100:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:101:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:102:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:124:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:125:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:126:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:127:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:128:3:
warning: UNKNOWN
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/init.c:129:3:
warning: UNKNOWN

testcase
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/analyzer.exp
completed in 1 seconds

                === gcc Summary ===

# of expected passes            27
# of unexpected failures        15

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

* [Bug testsuite/96609] new test case gcc.dg/analyzer/init.c has many failures
  2020-08-13 23:02 [Bug testsuite/96609] New: new test case gcc.dg/analyzer/init.c has many failures seurer at gcc dot gnu.org
@ 2020-08-14  4:40 ` seurer at gcc dot gnu.org
  2020-08-14 22:43 ` cvs-commit at gcc dot gnu.org
  2020-08-14 22:57 ` dmalcolm at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: seurer at gcc dot gnu.org @ 2020-08-14  4:40 UTC (permalink / raw)
  To: gcc-bugs

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

seurer at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Host|                            |powerpc64*-linux-gnu
             Target|                            |powerpc64*-linux-gnu
              Build|                            |powerpc64*-linux-gnu
                 CC|                            |bergner at gcc dot gnu.org,
                   |                            |dmalcolm at gcc dot gnu.org

--- Comment #1 from seurer at gcc dot gnu.org ---
Also these:

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/pr93032-mztools.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 -S -o pr93032-mztools.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/pr93032-mztools.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 -S -o pr93032-mztools.s
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:
In function 'unzRepair':
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:328:10:
warning: leak of FILE 'fpOutCD' [CWE-775] [-Wanalyzer-file-leak]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:78:19:
note: (1) opened here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:79:6:
note: (2) following 'false' branch (when 'fpZip' is NULL)...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:326:9:
note: (3) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:328:10:
note: (4) 'fpOutCD' leaks here; was opened at (1)
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:328:10:
warning: leak of FILE 'fpOut' [CWE-775] [-Wanalyzer-file-leak]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:77:17:
note: (1) opened here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:79:6:
note: (2) following 'false' branch (when 'fpZip' is NULL)...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:326:9:
note: (3) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:328:10:
note: (4) 'fpOut' leaks here; was opened at (1)
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:328:10:
warning: leak of FILE 'fpZip' [CWE-775] [-Wanalyzer-file-leak]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:76:17:
note: (1) opened here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:79:6:
note: (2) assuming 'fpZip' is non-NULL
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:79:6:
note: (3) following 'true' branch (when 'fpZip' is non-NULL)...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:79:21:
note: (4) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:79:21:
note: (5) following 'false' branch (when 'fpOut' is NULL)...
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:326:9:
note: (6) ...to here
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:328:10:
note: (7) 'fpZip' leaks here; was opened at (1)
PASS: gcc.dg/analyzer/pr93032-mztools.c leak of fpZip (test for warnings, line
328)
PASS: gcc.dg/analyzer/pr93032-mztools.c leak of fpOut (test for warnings, line
328)
PASS: gcc.dg/analyzer/pr93032-mztools.c leak of fpOutCD (test for warnings,
line 328)
Executing on host: /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/ exceptions_enabled30727.cc   
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never  -fdiagnostics-urls=never  -S -o
exceptions_enabled30727.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_enabled30727.cc
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -S -o
exceptions_enabled30727.s
FAIL: gcc.dg/analyzer/pr93032-mztools.c (test for excess errors)
Excess errors:
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/pr93032-mztools.c:261:11:
warning: terminating analysis for this program point: EN: 841-849
[-Wanalyzer-too-complex]

testcase
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/analyzer/analyzer.exp
completed in 1 seconds

                === gcc Summary ===

# of expected passes            3
# of unexpected failures        1

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

* [Bug testsuite/96609] new test case gcc.dg/analyzer/init.c has many failures
  2020-08-13 23:02 [Bug testsuite/96609] New: new test case gcc.dg/analyzer/init.c has many failures seurer at gcc dot gnu.org
  2020-08-14  4:40 ` [Bug testsuite/96609] " seurer at gcc dot gnu.org
@ 2020-08-14 22:43 ` cvs-commit at gcc dot gnu.org
  2020-08-14 22:57 ` dmalcolm at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-08-14 22:43 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:

https://gcc.gnu.org/g:2867118ddda9b56d991c16022f7d3d634ed08313

commit r11-2708-g2867118ddda9b56d991c16022f7d3d634ed08313
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Fri Aug 14 15:49:52 2020 -0400

    analyzer: fix initialization from constant pool [PR96609,PR96616]

    PR testsuite/96609 and PR analyzer/96616 report various testsuite
    failures seen on powerpc64, aarch64, and arm in new tests added by
    r11-2694-g808f4dfeb3a95f50f15e71148e5c1067f90a126d.

    Some of these failures (in gcc.dg/analyzer/init.c, and on arm
    in gcc.dg/analyzer/casts-1.c) relate to initializations from var_decls
    in the constant pool.  I wrote the tests assuming that the gimplified
    stmts would initialize the locals via a gassign of code CONSTRUCTOR,
    whereas on these targets some of the initializations are gassign from
    a VAR_DECL e.g.:
      c = *.LC0;
    where "*.LC0" is a var_decl with DECL_IN_CONSTANT_POOL set.

    For example, in test_7:
       struct coord c[2] = {{3, 4}, {5, 6}};
       __analyzer_eval (c[0].x == 3); /* { dg-warning "TRUE" } */
    after the initialization, the store was simply recording:
       cluster for: c: INIT_VAL(*.LC0)
    when I was expecting the cluster for c to have:
      cluster for: c
        key:   {kind: direct, start: 0, size: 32, next: 32}
        value: 'int' {(int)3}
        key:   {kind: direct, start: 32, size: 32, next: 64}
        value: 'int' {(int)4}
        key:   {kind: direct, start: 64, size: 32, next: 96}
        value: 'int' {(int)5}
        key:   {kind: direct, start: 96, size: 32, next: 128}
        value: 'int' {(int)6}
    The test for c[0].x == 3 would then generate:
      cluster for: _2: (SUB(SUB(INIT_VAL(*.LC0), c[(int)0]),
c[(int)0].x)==(int)3)
    which is UNKNOWN, leading to the test failing.

    This patch fixes the init.c and casts-1.c failures by special-casing
    reads from a var_decl with DECL_IN_CONSTANT_POOL set, so that they build
    a compound_svalue containing the bindings implied by the CONSTRUCTOR
    node for DECL_INITIAL.

    gcc/analyzer/ChangeLog:
            PR testsuite/96609
            PR analyzer/96616
            * region-model.cc (region_model::get_store_value): Call
            maybe_get_constant_value on decl_regions first.
            * region-model.h (decl_region::maybe_get_constant_value): New decl.
            * region.cc (decl_region::get_stack_depth): Likewise.
            (decl_region::maybe_get_constant_value): New.
            * store.cc (get_subregion_within_ctor): New.
            (binding_map::apply_ctor_to_region): New.
            * store.h (binding_map::apply_ctor_to_region): New decl.

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

* [Bug testsuite/96609] new test case gcc.dg/analyzer/init.c has many failures
  2020-08-13 23:02 [Bug testsuite/96609] New: new test case gcc.dg/analyzer/init.c has many failures seurer at gcc dot gnu.org
  2020-08-14  4:40 ` [Bug testsuite/96609] " seurer at gcc dot gnu.org
  2020-08-14 22:43 ` cvs-commit at gcc dot gnu.org
@ 2020-08-14 22:57 ` dmalcolm at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: dmalcolm at gcc dot gnu.org @ 2020-08-14 22:57 UTC (permalink / raw)
  To: gcc-bugs

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

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this.

r11-2708-g2867118ddda9b56d991c16022f7d3d634ed08313 should fix the init.c issue
mentioned in this bug's title, but not the issue in comment #1.

Both issues here are also being tracked by PR analyzer/96616 which has a more
generic title, so I'm going to close out this bug as a duplicate of that one.

*** This bug has been marked as a duplicate of bug 96616 ***

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

end of thread, other threads:[~2020-08-14 22:57 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-13 23:02 [Bug testsuite/96609] New: new test case gcc.dg/analyzer/init.c has many failures seurer at gcc dot gnu.org
2020-08-14  4:40 ` [Bug testsuite/96609] " seurer at gcc dot gnu.org
2020-08-14 22:43 ` cvs-commit at gcc dot gnu.org
2020-08-14 22:57 ` dmalcolm 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).