From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] PR 58102 aka DR 1405
Date: Tue, 02 Sep 2014 15:45:00 -0000 [thread overview]
Message-ID: <5405E617.9020507@redhat.com> (raw)
In-Reply-To: <5405DD3E.7030506@oracle.com>
On 09/02/2014 11:07 AM, Paolo Carlini wrote:
> Anyway, what about the below? Certainly works for the tests which we
> have got.
Hmm. This is definitely an improvement, as it allows a subset of
a non-volatile glvalue of literal type that refers to a non-volatile
object whose lifetime began within the evalution of e
But it doesn't cover all of that, and in any case we shouldn't need to
explicitly handle that just for types with mutable subobjects.
I think perhaps it would be better to remove that hunk as in your
initial patch and replace it with a check in constant_value_1 and an
explanation in non_const_var_error.
Jason
next prev parent reply other threads:[~2014-09-02 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 13:48 Paolo Carlini
2014-09-02 14:11 ` Jason Merrill
2014-09-02 14:17 ` Paolo Carlini
2014-09-02 14:28 ` Jason Merrill
2014-09-02 14:31 ` Paolo Carlini
2014-09-02 15:07 ` Paolo Carlini
2014-09-02 15:45 ` Jason Merrill [this message]
2014-09-03 10:53 ` Paolo Carlini
2014-09-03 20:33 ` Jason Merrill
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=5405E617.9020507@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paolo.carlini@oracle.com \
/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).