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/111475] New: Many C++ analyzer tests FAIL
Date: Tue, 19 Sep 2023 11:50:50 +0000 [thread overview]
Message-ID: <bug-111475-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111475
Bug ID: 111475
Summary: Many C++ analyzer 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
CC: vultkayn at gcc dot gnu.org
Target Milestone: ---
Target: *-*-solaris2.11
Between 20230908 (f9cb357ae962ba2922b8507f4d96227780a063b9) and 20230911
(88a0a883960910530bfefa750461168f539f4a00), man (ca.350 per multilib) analyzer
tests FAIL on Solaris (both 32 and 64-bit, SPARC and x86). There may be a
common pattern (I've only looked at one example):
FAIL: c-c++-common/analyzer/allocation-size-1.c -std=c++14 (test for
warnings, line 33)
FAIL: c-c++-common/analyzer/allocation-size-1.c -std=c++14 note (test for
warnings, line 65)
FAIL: c-c++-common/analyzer/allocation-size-1.c -std=c++14 note at line 21
(test for warnings, line 15)
Comparing the full output on Solaris
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:
In function 'void test_2()':
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:15:37:
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/allocation-size-1.c:15:37:
note: (1) allocated 42 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/allocation-size-1.c:
In function 'void test_4()':
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:34:12:
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/allocation-size-1.c:34:12:
note: (1) allocated 42 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/allocation-size-1.c:
In function 'void test_6()':
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:68:12:
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/allocation-size-1.c:68:12:
note: (1) allocated 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/allocation-size-1.c:
In function 'void test_11()':
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:125:37:
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/allocation-size-1.c:125:37:
note: (1) allocated 3 bytes and assigned to 'int32_t*' {aka 'int*'} here;
'sizeof (int32_t {aka int})' is '4'
and Linux
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:
In function 'void test_2()':
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:15:37:
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/allocation-size-1.c:15:37:
note: (1) allocated 42 bytes here
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:15:37:
note: (2) 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/allocation-size-1.c:
In function 'void test_4()':
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:34:12:
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/allocation-size-1.c:33:22:
note: (1) allocated 42 bytes here
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:34:12:
note: (2) 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/allocation-size-1.c:
In function 'void test_6()':
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:68:12:
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/allocation-size-1.c:65:22:
note: (1) allocated here
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:68:12:
note: (2) 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/allocation-size-1.c:
In function 'void test_11()':
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:125:37:
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/allocation-size-1.c:125:37:
note: (1) allocated 3 bytes here
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:125:37:
note: (2) assigned to 'int32_t*' {aka 'int*'} here; 'sizeof (int32_t {aka
int})' is '4'
ISTM that the primary difference is here:
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:15:37:
note: (1) allocated 42 bytes and assigned to 'int32_t*' {aka 'int*'} here;
'sizeof (int32_t {aka int})' is '4'
vs.
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:15:37:
note: (1) allocated 42 bytes here
/vol/gcc/src/hg/master/local/gcc/testsuite/c-c++-common/analyzer/allocation-size-1.c:15:37:
note: (2) assigned to 'int32_t*' {aka 'int*'} here; 'sizeof (int32_t {aka
int})' is '4'
i.e. the wording of the note, where the testsuite doesn't cater to the first
form.
This creates an incredible amount of noise, unfortunately.
next reply other threads:[~2023-09-19 11:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 11:50 ro at gcc dot gnu.org [this message]
2023-09-19 11:51 ` [Bug analyzer/111475] " ro at gcc dot gnu.org
2024-01-18 12:52 ` ro at gcc dot gnu.org
2024-01-18 15:16 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-01-19 10:10 ` ro at gcc dot gnu.org
2024-01-19 10:11 ` ro at gcc dot gnu.org
2024-01-19 10:11 ` ro at gcc dot gnu.org
2024-04-23 13:46 ` [Bug analyzer/111475] [14 regression] " ro at gcc dot gnu.org
2024-04-23 17:16 ` ro at gcc dot gnu.org
2024-04-26 13:06 ` [Bug analyzer/111475] [14/15 " ro at gcc dot gnu.org
2024-04-26 13:15 ` dmalcolm at gcc dot gnu.org
2024-04-26 13:36 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-04-30 19:43 ` dmalcolm at gcc dot gnu.org
2024-05-01 10:29 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-03 13:12 ` cvs-commit at gcc dot gnu.org
2024-05-03 13:34 ` [Bug analyzer/111475] [14 " dmalcolm at gcc dot gnu.org
2024-05-06 8:55 ` cvs-commit 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-111475-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).