https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110483
Bug ID: 110483
Summary: Several gcc.dg/analyzer/out-of-bounds-diagram-*.c
tests FAIL
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
Target Milestone: ---
Target: sparc*-sun-solaris2.11, pru-unknown-elf,
powerpc-ibm-aix7.2.5.0, avr-unknown-none
Several of the new gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL on
Solaris/SPARC (32 and 64-bit):
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-13.c (test for excess errors)
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-13.c 2 blank line(s) in output
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-13.c expected multiline pattern
lines 17-42
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-15.c (test for excess errors)
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-15.c 2 blank line(s) in output
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-15.c expected multiline pattern
lines 16-41
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-4.c (test for excess errors)
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-4.c 2 blank line(s) in output
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-4.c expected multiline pattern
lines 23-44
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-5-ascii.c (test for excess errors)
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-5-ascii.c 2 blank line(s) in
output
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-5-ascii.c expected multiline
pattern lines 16-39
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-5-unicode.c (test for excess
errors)
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-5-unicode.c 2 blank line(s) in
output
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-5-unicode.c expected multiline
pattern lines 16-41
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-7.c (test for excess errors)
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-7.c 2 blank line(s) in output
+FAIL: gcc.dg/analyzer/out-of-bounds-diagram-7.c expected multiline pattern
lines 14-35
I also see gcc-testresults reports for several other targets, but it's
difficult
to the if that's the same issue without the actual gcc.log.
E.g. for
FAIL: gcc.dg/analyzer/out-of-bounds-diagram-5-unicode.c (test for excess
errors)
the log shows
Excess errors:
┌─────┬─────┬─────┬────┬────┐┌────┬────┬────┬────┬────┬────┬────┬──────┐
│ [0] │ [0] │ [0] │[0] │[0] ││[0] │[0] │[0] │[0] │[0] │[0] │[0] │ [0] │
├─────┼─────┼─────┼────┼────┤├────┼────┼────┼────┼────┼────┼────┼──────┤
│0xe6 │0x96 │0x87 │0xe5│0xad││0x97│0xe5│0x8c│0x96│0xe3│0x81│0x91│ 0x00 │
├─────┴─────┴─────┼────┴────┴┴────┼────┴────┴────┼────┴────┴────┼──────┤
│ U+6587 │ U+5b57 │ U+5316 │ U+3051 │U+0000│
├─────────────────┼───────────────┼──────────────┼──────────────┼──────┤
│ 文 │ 字 │ 化 │ け │ NUL │
├─────────────────┴───────────────┴──────────────┴──────────────┴──────┤
│ string literal (type: 'char[13]') │
└──────────────────────────────────────────────────────────────────────┘
│ │ │ │ │ │ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │ │ │ │ │ │
v v v v v v v v v v v v v
┌─────┬────────────────┬────┐┌─────────────────────────────────────────┐
│ [0] │ ... │[4] ││ │
├─────┴────────────────┴────┤│ after valid range │
│ 'buf' (type: 'char[5]') ││ │
└───────────────────────────┘└─────────────────────────────────────────┘
├─────────────┬─────────────┤├────────────────────┬────────────────────┤
│ │
╭────────┴────────╮ ╭─────────┴─────────╮
│capacity: 5 bytes│ │overflow of 8 bytes│
╰─────────────────╯ ╰───────────────────╯
while the test expects
│ [0] │ [1] │ [2] │[3] │[4] ││[5] │[6] │[7] │[8] │[9] │[10]│[11]│ [12] │
above.
