public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104373] [12 regression] bogus -Wmaybe-uninitialized warning with array new
Date: Thu, 10 Feb 2022 23:28:52 +0000 [thread overview]
Message-ID: <bug-104373-4-VFIlkhBNZ9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104373-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104373
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:50243f4918c2ed7f1ddbf0e8df97a37aee73ebf2
commit r12-7188-g50243f4918c2ed7f1ddbf0e8df97a37aee73ebf2
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Feb 11 00:27:11 2022 +0100
testsuite: Fix up g++.dg/warn/Wuninitialized-32.C test for ilp32 [PR104373]
The testcase FAILs whenever size_t is not unsigned long:
FAIL: g++.dg/warn/Wuninitialized-32.C -std=c++98 (test for excess errors)
Excess errors:
.../gcc/testsuite/g++.dg/warn/Wuninitialized-32.C:4:7: error: 'operator
new' takes type 'size_t' ('unsigned int') as first parameter [-fpermissive]
Fixed by using __SIZE_TYPE__ instead of unsigned long.
2022-02-11 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/104373
* g++.dg/warn/Wuninitialized-32.C (operator new[]): Use
__SIZE_TYPE__
as type of the first argument instead of unsigned long.
prev parent reply other threads:[~2022-02-10 23:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 20:34 [Bug c++/104373] New: " sss@li-snyder.org
2022-02-04 0:12 ` [Bug c++/104373] " pinskia at gcc dot gnu.org
2022-02-04 0:21 ` [Bug tree-optimization/104373] " pinskia at gcc dot gnu.org
2022-02-04 8:24 ` rguenth at gcc dot gnu.org
2022-02-04 8:54 ` rguenth at gcc dot gnu.org
2022-02-10 11:51 ` cvs-commit at gcc dot gnu.org
2022-02-10 11:52 ` rguenth at gcc dot gnu.org
2022-02-10 23:28 ` cvs-commit at gcc dot gnu.org [this message]
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-104373-4-VFIlkhBNZ9@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).