From: Jason Merrill <jason@redhat.com>
To: Marek Polacek <polacek@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH for c++/86063, ICE with attribute with pack expansion
Date: Thu, 14 Jun 2018 20:46:00 -0000 [thread overview]
Message-ID: <CADzB+2=8d9+KV+O8SkkarnqKExYgkGBLow1QZfYiHaydT+zy=w@mail.gmail.com> (raw)
In-Reply-To: <20180614194052.GH17989@redhat.com>
On Thu, Jun 14, 2018 at 3:40 PM, Marek Polacek <polacek@redhat.com> wrote:
> On Thu, Jun 14, 2018 at 12:59:00PM -0400, Jason Merrill wrote:
>> On Thu, Jun 14, 2018 at 12:51 PM, Marek Polacek <polacek@redhat.com> wrote:
>> > On Mon, Jun 11, 2018 at 03:00:04PM -0400, Jason Merrill wrote:
>> >> On Wed, Jun 6, 2018 at 5:18 PM, Marek Polacek <polacek@redhat.com> wrote:
>> >> > We crash on this testcase containing a bogus attribute, because
>> >> > cp_check_const_attributes accessed TREE_VALUE of a tree that happened to be
>> >> > expr_pack_expansion. Since here we're merely trying to evaluate constexpr
>> >> > arguments, I thought we could skip such bogus arguments.
>> >>
>> >> Hmm, attributes should always be a TREE_LIST, lots of places assume
>> >> that. Why isn't the pack expansion wrapped in a TREE_LIST?
>> >
>> > I believe you did that on purpose. There pack comes from
>> > cp_parser_std_attribute_list. We could wrap it into a TREE_LIST, but then
>> > tsubst_attribute would have to be tweaked to handle the pack expansion
>> > correctly.
>>
>> How so? tsubst_attribute expects to find a pack expansion in the
>> TREE_VALUE of a TREE_LIST.
>> And cp_parser_std_attribute_list puts the pack expansion in TREE_VALUE.
>
> Exactly. But what tsubst_attribute gets currently is
>
> <tree_list 0x7ffff001c280 tree_0
> purpose <tree_list 0x7ffff0002f00
> purpose <identifier_node 0x7fffefec7d80 gnu
> normal local bindings <(nil)>>
> value <identifier_node 0x7ffff0014f00 aligned
> normal local bindings <(nil)>>>
> value <expr_pack_expansion 0x7fffefeada20
> arg:0 <tree_list 0x7ffff0002f50
> value <alignof_expr 0x7ffff0015600 type <integer_type 0x7fffefecd7e0 long unsigned int>
> readonly tree_0 arg:0 <template_type_parm 0x7ffff001a1f8 T>
> alignas4.C:17:19 start: alignas4.C:17:19 finish: alignas4.C:17:29>>
> arg:1 <tree_list 0x7ffff0002f78 value <template_type_parm 0x7ffff001a1f8 T>>>>
>
> so if I were to wrap the expr_pack_expansion in a TREE_LIST, I would have to adjust
> tsubst_attribute. But cp_check_const_attributes doesn't expect that the TREE_VALUE
> of the above is a non-list. Right?
Ah, of course, you're already looking at the arguments, I wasn't
reading closely enough. The patch is OK.
Jason
prev parent reply other threads:[~2018-06-14 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 21:18 Marek Polacek
2018-06-11 19:00 ` Jason Merrill
2018-06-14 16:51 ` Marek Polacek
2018-06-14 16:59 ` Jason Merrill
2018-06-14 19:40 ` Marek Polacek
2018-06-14 20:46 ` Jason Merrill [this message]
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='CADzB+2=8d9+KV+O8SkkarnqKExYgkGBLow1QZfYiHaydT+zy=w@mail.gmail.com' \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=polacek@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).