From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch] PR 84330 ("[6/7/8 Regression] [concepts] ICE with broken constraint")
Date: Thu, 15 Feb 2018 17:57:00 -0000 [thread overview]
Message-ID: <CADzB+2n3Bn06F8Uj0bW6vumG_5Yf3iwoM3e6Myho-0UE=My+QQ@mail.gmail.com> (raw)
In-Reply-To: <727ee55c-b5ec-e502-3c49-4ded00f11e3d@oracle.com>
OK.
On Thu, Feb 15, 2018 at 9:29 AM, Paolo Carlini <paolo.carlini@oracle.com> wrote:
> Hi,
>
> we have been accumulating quite a few bugs under the [concepts] meta-bug,
> most of which of course aren't regressions. This one is a low hanging fruit,
> an error recovery issue where, after some meaningful diagnostic,
> tsubst_constraint doesn't know how to handle an error_mark_node. I believe
> that ideally we should do better, we should be able to issue only the first
> error - I think a TODO in diagnose_constraint hints at that too - but the
> below should do for now (well, in 6.1.0 we issued *3* errors ;-)
>
> Thanks, Paolo.
>
> ////////////////////
>
prev parent reply other threads:[~2018-02-15 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 14:29 Paolo Carlini
2018-02-15 17:57 ` 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+2n3Bn06F8Uj0bW6vumG_5Yf3iwoM3e6Myho-0UE=My+QQ@mail.gmail.com' \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.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).