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++/97597] [11 Regression] ICE in build_over_call, at cp/call.c:9034
Date: Wed, 23 Dec 2020 22:11:29 +0000 [thread overview]
Message-ID: <bug-97597-4-6gXEQNe8Kq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97597-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97597
--- Comment #3 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:612cf351c700b6216209e3f3f4b3a0959bf2dee7
commit r11-6324-g612cf351c700b6216209e3f3f4b3a0959bf2dee7
Author: Jason Merrill <jason@redhat.com>
Date: Tue Dec 22 15:41:56 2020 -0500
c++: Fix initializing empty base from prvalue [PR97597]
unsafe_return_slot_p wasn't recognizing an empty base as
potentially-overlapping, which it definitely is.
The change to build_base_path is to make the virtual conversion also
recognized by is_empty_base_ref; unsafe_return_slot_p doesn't to handle
virtual conversions, but hypothetical future callers might.
gcc/cp/ChangeLog:
PR c++/97597
* class.c (is_empty_base_ref): New.
(build_base_path): Add NOP_EXPR after offset.
* cp-tree.h (is_empty_base_ref): Declare it.
* call.c (unsafe_return_slot_p): Call it.
gcc/testsuite/ChangeLog:
PR c++/97597
* g++.dg/init/empty3.C: New test.
next prev parent reply other threads:[~2020-12-23 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 15:46 [Bug c++/97597] New: " asolokha at gmx dot com
2020-10-27 15:48 ` [Bug c++/97597] " mpolacek at gcc dot gnu.org
2020-10-27 15:50 ` mpolacek at gcc dot gnu.org
2020-12-22 19:47 ` jason at gcc dot gnu.org
2020-12-23 22:11 ` cvs-commit at gcc dot gnu.org [this message]
2021-01-21 16:52 ` jason 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-97597-4-6gXEQNe8Kq@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).