public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Nathan Sidwell <nathan@acm.org>
Subject: Re: [C++ PING] Re: [C++ Patch, V2] PR 82593 ("Internal compiler error: in process_init_constructor_array, at cp/typeck2.c:1294")
Date: Tue, 19 Dec 2017 20:41:00 -0000	[thread overview]
Message-ID: <e17bf804-cc4b-17f4-cb2c-1028a3d373f1@redhat.com> (raw)
In-Reply-To: <44c93777-3841-e600-441d-0d616c357e0b@oracle.com>

On 11/30/2017 01:19 PM, Paolo Carlini wrote:
> On 17/11/2017 15:09, Paolo Carlini wrote:
>> Hi again,
>>
>> I managed to spend much more time on the issue and I'm starting a new 
>> thread with a mature - IMHO - proposal: the big thing is the use of 
>> the existing check_array_designated_initializer in 
>> process_init_constructor_array,  which calls maybe_constant_value, as 
>> we want, and covers all the ill-formed cases which I can imagine. I'm 
>> also tweaking a bit the parser to check the return value of 
>> require_potential_rvalue_constant_expression in order to avoid 
>> redundant diagnostic in some cases. Also, a couple more testcases 
>> beyond the bug report.
> I'm gently pinging this. I rebased it vs a very minor conflict due to 
> Jakub's implementation of P0329R4. While I was at it, I'm also proposing 
> a small tweak vs the previous version in the way 
> check_array_designated_initializer is used: only if ce->index is 
> non-null, more consistently with the current code.

OK.

Jason

      reply	other threads:[~2017-12-19 20:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 14:43 Paolo Carlini
2017-11-30 18:23 ` [C++ PING] " Paolo Carlini
2017-12-19 20:41   ` 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=e17bf804-cc4b-17f4-cb2c-1028a3d373f1@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nathan@acm.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).