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] [14 Regression] Several gcc.dg/analyzer/out-of-bounds-diagram-*.c tests FAIL Date: Thu, 29 Feb 2024 10:30:12 +0000 [thread overview] Message-ID: <bug-110483-4-3M2qAs4BNE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110483-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110483 Rainer Orth <ro at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2024-02-29 Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #5 from Rainer Orth <ro at gcc dot gnu.org> --- Thanks for the patch. Last night's bootstrap showed that all C tests PASS now. However, two of the tests FAIL when compiled as C++: FAIL: c-c++-common/analyzer/out-of-bounds-diagram-3.c -std=c++98 (test for warnings, line 25) FAIL: c-c++-common/analyzer/out-of-bounds-diagram-3.c -std=c++98 at line 20 (test for warnings, line 19) FAIL: c-c++-common/analyzer/out-of-bounds-diagram-3.c -std=c++98 expected multiline pattern lines 30-45 and same for -std=c++(14|17|20). When compiling manually, there's no output at all. There's also FAIL: c-c++-common/analyzer/out-of-bounds-diagram-11.c -std=c++98 (test for warnings, line 12) FAIL: c-c++-common/analyzer/out-of-bounds-diagram-11.c -std=c++98 expected multiline pattern lines 18-36 Here's the full output: /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c: In function ‘void test7(std::size_t)’: /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c:41:47: warning: allocated buffer size is not a multiple of the pointee's size [CWE-131] [-Wanalyzer-allocation-size] /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c:41:47: note: (1) allocated ‘((size * 4) + 3)’ bytes and assigned to ‘int32_t*’ {aka ‘int*’} here; ‘sizeof (int32_t {aka int})’ is ‘4’ /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c:42:13: warning: stack-based buffer overflow [CWE-121] [-Wanalyzer-out-of-bounds] /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c:41:47: note: (1) capacity: ‘((size * 4) + 3)’ bytes /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c:42:13: note: (2) write of 4 bytes at offset ‘(size * 4)’ exceeds the buffer ┌───────────────────────────────────────┐ │ write of ‘(int) 42’ │ └───────────────────────────────────────┘ │ │ │ │ v v ┌──────────────────────────────────────────────────┐┌──────────────────┐ │ buffer allocated on stack at (1) ││after valid range │ └──────────────────────────────────────────────────┘└──────────────────┘ ├────────────────────────┬─────────────────────────┤├────────┬─────────┤ │ │ ╭───────────────┴──────────────╮ ╭─────────┴────────╮ │capacity: ‘size * 4 + 3’ bytes│ │overflow of 1 byte│ ╰──────────────────────────────╯ ╰──────────────────╯ /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c: In function ‘char* test99(const char*, const char*)’: /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c:80:25: warning: heap-based buffer overflow [CWE-122] [-Wanalyzer-out-of-bounds] /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c:74:44: note: (1) capacity: ‘(len_x + len_y)’ bytes /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c:75:3: note: (2) following ‘false’ branch (when ‘result’ is non-NULL)... /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c:77:20: note: (3) ...to here /vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/out-of-bounds-diagram-11.c:80:25: note: (4) out-of-bounds write I'm uncertain if this isn't another issue, though.
next prev parent reply other threads:[~2024-02-29 10:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-29 11:09 [Bug analyzer/110483] New: " ro at gcc dot gnu.org 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 [this message] 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-3M2qAs4BNE@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).