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 c++/100111] [10 Regression] `-fno-elide-constructors` with `constexpr` ctors causes ICE in GCC 10.3
Date: Tue, 20 Apr 2021 09:46:29 +0000 [thread overview]
Message-ID: <bug-100111-4-ffkvBT4IwL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100111-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100111
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:31447dcaf15c37e5b9c42b2984f4c8b649fe9b74
commit r10-9730-g31447dcaf15c37e5b9c42b2984f4c8b649fe9b74
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Apr 16 17:37:07 2021 +0200
c++: Fix empty base stores in cxx_eval_store_expression [PR100111]
In r11-6895 handling of empty bases has been fixed such that non-lval
stores of empty classes are not added when the type of *valp doesn't
match the type of the initializer, but as this testcase shows it is
done only when *valp is non-NULL. If it is NULL, we still shouldn't
add empty class constructors if the type of the constructor elt *valp
points to doesn't match.
2021-04-16 Jakub Jelinek <jakub@redhat.com>
PR c++/100111
* constexpr.c (cxx_eval_store_expression): Don't add CONSTRUCTORs
for empty classes into *valp when types don't match even when *valp
is NULL.
* g++.dg/cpp0x/constexpr-100111.C: New test.
(cherry picked from commit 35e8b38a91d9fb49a4759649576f15e76c129d99)
next prev parent reply other threads:[~2021-04-20 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 5:37 [Bug c++/100111] New: `-fno-elide-constructors` " lh_mouse at 126 dot com
2021-04-16 7:36 ` [Bug c++/100111] [10/11 Regression] `-fno-elide-constructors` with `constexpr` ctors " rguenth at gcc dot gnu.org
2021-04-16 8:14 ` jakub at gcc dot gnu.org
2021-04-16 9:04 ` jakub at gcc dot gnu.org
2021-04-16 10:16 ` jakub at gcc dot gnu.org
2021-04-16 11:11 ` lh_mouse at 126 dot com
2021-04-16 14:01 ` lh_mouse at 126 dot com
2021-04-16 14:10 ` jason at gcc dot gnu.org
2021-04-16 15:44 ` cvs-commit at gcc dot gnu.org
2021-04-17 3:33 ` [Bug c++/100111] [10 " jason at gcc dot gnu.org
2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-20 9:53 ` jakub at gcc dot gnu.org
2022-04-13 14:18 ` cvs-commit at gcc dot gnu.org
2022-05-06 20:30 ` cvs-commit at gcc dot gnu.org
2022-05-12 20:13 ` cvs-commit at gcc dot gnu.org
2022-05-12 21:15 ` 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-100111-4-ffkvBT4IwL@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).