public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/110483] New: Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL
Date: Thu, 29 Jun 2023 11:09:36 +0000	[thread overview]
Message-ID: <bug-110483-4@http.gcc.gnu.org/bugzilla/> (raw)

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.

             reply	other threads:[~2023-06-29 11:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 11:09 ro at gcc dot gnu.org [this message]
2023-06-29 11:10 ` [Bug analyzer/110483] " ro at gcc dot gnu.org
2023-06-29 20:22 ` dmalcolm at gcc dot gnu.org
2023-06-30 12:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-02-27 22:19 ` [Bug analyzer/110483] [14 Regression] " cvs-commit at gcc dot gnu.org
2024-02-27 22:29 ` dmalcolm at gcc dot gnu.org
2024-02-29 10:30 ` ro at gcc dot gnu.org
2024-02-29 16:08 ` dmalcolm at gcc dot gnu.org
2024-02-29 20:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-07  7:40 ` [Bug analyzer/110483] [14/15 " rguenth 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-110483-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).