From: Paolo Carlini <paolo.carlini@oracle.com>
To: gcc-patches@gcc.gnu.org
Cc: Jason Merrill <jason@redhat.com>, Nathan Sidwell <nathan@acm.org>
Subject: Re: [C++ Patch] PR 84644 ("internal compiler error: in warn_misplaced_attr_for_class_type, at cp/decl.c:4718")
Date: Fri, 26 Oct 2018 09:37:00 -0000 [thread overview]
Message-ID: <4c6fe735-5435-1ede-a85a-787262a7e63c@oracle.com> (raw)
In-Reply-To: <b119ff96-b338-317f-c425-d997874589e4@redhat.com>
Hi,
On 24/10/18 22:41, Jason Merrill wrote:
> On 10/15/18 12:45 PM, Paolo Carlini wrote:
>> Â Â Â Â Â Â Â && ((TREE_CODE (declspecs->type) != TYPENAME_TYPE
>> +Â Â Â Â Â Â && TREE_CODE (declspecs->type) != DECLTYPE_TYPE
>> Â Â Â Â Â Â Â Â && MAYBE_CLASS_TYPE_P (declspecs->type))
>
> I would think that the MAYBE_CLASS_TYPE_P here should be CLASS_TYPE_P,
> and then we can remove the TYPENAME_TYPE check. Or do we want to
> allow template type parameters for some reason?
Indeed, it would be nice to just use OVERLOAD_TYPE_P. However it seems
we at least want to let through TEMPLATE_TYPE_PARMs representing 'auto'
- otherwise Dodji's check a few lines below which fixed c++/51473
doesn't work anymore - and also BOUND_TEMPLATE_TEMPLATE_PARM, otherwise
we regress on template/spec32.C and template/ttp22.C because we don't
diagnose the shadowing anymore. Thus, I would say either we keep on
using MAYBE_CLASS_TYPE_P or we pick what we need, possibly we add a comment?
Thanks, Paolo.
next prev parent reply other threads:[~2018-10-26 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 18:21 Paolo Carlini
2018-10-24 21:56 ` Jason Merrill
2018-10-26 9:37 ` Paolo Carlini [this message]
2018-10-26 16:28 ` Jason Merrill
2018-10-26 19:03 ` Paolo Carlini
2018-10-30 21:46 ` Jason Merrill
2018-10-31 5:25 ` Paolo Carlini
2018-12-13 22:22 ` Jason Merrill
2018-12-14 18:44 ` Paolo Carlini
2018-12-14 20:19 ` Jason Merrill
2018-12-14 21:34 ` Paolo Carlini
2018-12-14 21:43 ` 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=4c6fe735-5435-1ede-a85a-787262a7e63c@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=nathan@acm.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).