From: Jason Merrill <jason@redhat.com>
To: Mikhail Maltsev <maltsevm@gmail.com>, gcc-patches <gcc-patches@gnu.org>
Subject: Re: [PATCH][C++] Fix PR67333
Date: Tue, 06 Oct 2015 13:47:00 -0000 [thread overview]
Message-ID: <5613D0CA.1070706@redhat.com> (raw)
In-Reply-To: <55DF5684.8050607@gmail.com>
Hi, sorry for the slow response. Please feel free to ping once a week.
On 08/27/2015 02:27 PM, Mikhail Maltsev wrote:
> + if (TREE_THIS_VOLATILE (t) && (!DECL_P (t) || want_rval))
Why the !DECL_P check? Pulling the value out of a volatile INDIRECT_REF
is just as problematic as from a variable.
Jason
next prev parent reply other threads:[~2015-10-06 13:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 18:35 Mikhail Maltsev
2015-09-16 6:09 ` [PATCH][PING][C++] " Mikhail Maltsev
2015-10-05 23:47 ` [PATCH][PING^2][C++] " Mikhail Maltsev
2015-10-06 13:47 ` Jason Merrill [this message]
2015-10-17 19:49 ` [PATCH][C++] " Mikhail Maltsev
2015-10-18 9:31 ` 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=5613D0CA.1070706@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gnu.org \
--cc=maltsevm@gmail.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).