public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/70690] [6/7 Regression] r235002 miscompiles tcmalloc
[not found] <bug-70690-4@http.gcc.gnu.org/bugzilla/>
@ 2021-11-15 7:50 ` cvs-commit at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: cvs-commit at gcc dot gnu.org @ 2021-11-15 7:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70690
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
https://gcc.gnu.org/g:bd95d75f3412e1a7debab7c6c602ba409f274eb5
commit r12-5254-gbd95d75f3412e1a7debab7c6c602ba409f274eb5
Author: Jason Merrill <jason@redhat.com>
Date: Thu Nov 11 22:03:53 2021 -0500
c++: c++20 constexpr default ctor and array init
The implicit constexpr patch revealed that marking the constructor in the
PR70690 testcase as constexpr made the bug reappear, because build_vec_init
assumed that a constexpr default constructor initialized the whole object,
so it was equivalent to value-initialization. But this is no longer true
in
C++20.
PR c++/70690
gcc/cp/ChangeLog:
* init.c (build_vec_init): Check default_init_uninitialized_part in
C++20.
gcc/testsuite/ChangeLog:
* g++.dg/init/array41a.C: New test.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-11-15 7:50 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-70690-4@http.gcc.gnu.org/bugzilla/>
2021-11-15 7:50 ` [Bug c++/70690] [6/7 Regression] r235002 miscompiles tcmalloc cvs-commit at gcc dot gnu.org
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).