public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/111377] New: [14 regression] c-c++-common/analyzer/compound-assignment-1.c fails after XXX on big endian
Date: Mon, 11 Sep 2023 18:49:52 +0000	[thread overview]
Message-ID: <bug-111377-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111377
           Summary: [14 regression]
                    c-c++-common/analyzer/compound-assignment-1.c fails
                    after XXX on big endian
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

g:50b5199cff690891726877e1c00ac53dfb7cc1c8, r14-3823-g50b5199cff6908


This fails just on BE for me.

make  -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32,m64}'
analyzer.exp=c-c++-common/analyzer/compound-assignment-1.c"
FAIL: c-c++-common/analyzer/compound-assignment-1.c  -std=c++98  (test for
warnings, line 72)
FAIL: c-c++-common/analyzer/compound-assignment-1.c  -std=c++98 (test for
excess errors)
FAIL: c-c++-common/analyzer/compound-assignment-1.c  -std=c++14  (test for
warnings, line 72)
FAIL: c-c++-common/analyzer/compound-assignment-1.c  -std=c++14 (test for
excess errors)
FAIL: c-c++-common/analyzer/compound-assignment-1.c  -std=c++17  (test for
warnings, line 72)
FAIL: c-c++-common/analyzer/compound-assignment-1.c  -std=c++17 (test for
excess errors)
FAIL: c-c++-common/analyzer/compound-assignment-1.c  -std=c++20  (test for
warnings, line 72)
FAIL: c-c++-common/analyzer/compound-assignment-1.c  -std=c++20 (test for
excess errors)


spawn -ignore SIGHUP
/home/seurer/gcc/git/build/gcc-test2/gcc/testsuite/g++/../../xg++
-B/home/seurer/gcc/git/build/gcc-test2/gcc/testsuite/g++/../../
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c
-m32 -fdiagnostics-plain-output -nostdinc++
-I/home/seurer/gcc/git/build/gcc-test2/powerpc64-unknown-linux-gnu/32/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/git/build/gcc-test2/powerpc64-unknown-linux-gnu/32/libstdc++-v3/include
-I/home/seurer/gcc/git/gcc-test2/libstdc++-v3/libsupc++
-I/home/seurer/gcc/git/gcc-test2/libstdc++-v3/include/backward
-I/home/seurer/gcc/git/gcc-test2/libstdc++-v3/testsuite/util -fmessage-length=0
-std=c++20 -fanalyzer -Wanalyzer-too-complex -fanalyzer-call-summaries -S -o
compound-assignment-1.s
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:
In function 'void test_4()':
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:42:1:
warning: leak of 'r.ptr_wrapper::ptr' [CWE-401] [-Wanalyzer-malloc-leak]
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:41:26:
note: (1) allocated here
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:42:1:
note: (2) 'r.ptr_wrapper::ptr' leaks here; was allocated at (1)
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:
In function 'void test_5a()':
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:57:1:
warning: leak of 'q.ptr_wrapper::ptr' [CWE-401] [-Wanalyzer-malloc-leak]
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:54:6:
note: (1) entry to 'test_5a'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:56:44:
note: (2) calling 'called_by_test_5a' from 'test_5a'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:47:1:
note: (3) entry to 'called_by_test_5a'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:50:26:
note: (4) allocated here
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:56:44:
note: (5) returning to 'test_5a' from 'called_by_test_5a'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:57:1:
note: (6) 'q.ptr_wrapper::ptr' leaks here; was allocated at (4)
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:
In function 'void test_5b()':
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:71:21:
warning: leak of '<anonymous>.ptr_wrapper::ptr' [CWE-401]
[-Wanalyzer-malloc-leak]
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:69:6:
note: (1) entry to 'test_5b'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:71:21:
note: (2) calling 'called_by_test_5b' from 'test_5b'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:61:1:
note: (3) entry to 'called_by_test_5b'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:64:26:
note: (4) allocated here
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:71:21:
note: (5) returning to 'test_5b' from 'called_by_test_5b'
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:71:21:
note: (6) '<anonymous>.ptr_wrapper::ptr' leaks here; was allocated at (4)
PASS: c-c++-common/analyzer/compound-assignment-1.c  -std=c++20  (test for
warnings, line 41)
PASS: c-c++-common/analyzer/compound-assignment-1.c  -std=c++20  at line 43
(test for warnings, line 42)
PASS: c-c++-common/analyzer/compound-assignment-1.c  -std=c++20 unknown leak at
line 44 (test for bogus messages, line 43)
PASS: c-c++-common/analyzer/compound-assignment-1.c  -std=c++20  (test for
warnings, line 50)
PASS: c-c++-common/analyzer/compound-assignment-1.c  -std=c++20  at line 58
(test for warnings, line 57)
FAIL: c-c++-common/analyzer/compound-assignment-1.c  -std=c++20  (test for
warnings, line 72)
FAIL: c-c++-common/analyzer/compound-assignment-1.c  -std=c++20 (test for
excess errors)
Excess errors:
/home/seurer/gcc/git/gcc-test2/gcc/testsuite/c-c++-common/analyzer/compound-assignment-1.c:71:21:
warning: leak of '<anonymous>.ptr_wrapper::ptr' [CWE-401]
[-Wanalyzer-malloc-leak]


commit 50b5199cff690891726877e1c00ac53dfb7cc1c8 (HEAD)
Author: benjamin priour <vultkayn@gcc.gnu.org>
Date:   Sat Sep 9 18:03:56 2023 +0200

    analyzer: Move gcc.dg/analyzer tests to c-c++-common (2) [PR96395]

             reply	other threads:[~2023-09-11 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 18:49 seurer at gcc dot gnu.org [this message]
2023-09-11 18:57 ` [Bug other/111377] " jakub at gcc dot gnu.org
2023-09-11 19:21 ` pinskia at gcc dot gnu.org
2023-09-12  6:55 ` [Bug other/111377] [14 regression] c-c++-common/analyzer/compound-assignment-1.c fails after r14-3823-g50b5199cff6908 " jakub at gcc dot gnu.org
2023-09-12 12:26 ` [Bug testsuite/111377] " rguenth at gcc dot gnu.org
2023-09-19 15:49 ` cvs-commit at gcc dot gnu.org
2023-09-19 15:50 ` jakub 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-111377-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).