From: Paolo Carlini <paolo.carlini@oracle.com>
To: Jason Merrill <jason@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] PR 65815
Date: Mon, 08 Jun 2015 21:22:00 -0000 [thread overview]
Message-ID: <5575FBFD.7090208@oracle.com> (raw)
In-Reply-To: <5575BFE7.60200@redhat.com>
Hi,
On 06/08/2015 06:16 PM, Jason Merrill wrote:
> On 05/22/2015 02:46 PM, Paolo Carlini wrote:
>> take a type, not a decl, as first argument.
>
> Why? This complicates calls.
Yes, but, on the other hand, it's more consistent with the arguments of
the various digest_init_*. Also, we don't really use the DECL per se,
*only* its TREE_TYPE in the body. Thus, all in all, I decided to propose
that, but sure, I don't have a strong opinion...
> Could you also check that we do the right thing for mem-initializers?
Sure I will.
Paolo.
next prev parent reply other threads:[~2015-06-08 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 19:57 Paolo Carlini
2015-06-08 15:53 ` [Ping] " Paolo Carlini
2015-06-08 16:51 ` Jason Merrill
2015-06-08 21:22 ` Paolo Carlini [this message]
2015-06-08 23:20 ` Paolo Carlini
2015-06-09 0:58 ` Paolo Carlini
2015-06-09 14:05 ` 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=5575FBFD.7090208@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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).