From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: Bunch of location improvements
Date: Mon, 09 Sep 2019 21:01:00 -0000 [thread overview]
Message-ID: <6ababa8d-4eca-dd6a-c8e2-313918687751@redhat.com> (raw)
In-Reply-To: <8f2d7681-ce1f-15e9-02cf-b8fc83c6f284@oracle.com>
On 9/2/19 9:28 AM, Paolo Carlini wrote:
> Hi,
>
> all should be more or less straightforward. I also propose to use an
> additional range for that error message about constinit && constexpr
> mentioned to Marek a few days ago. Tested x86_64-linux.
>
> Thanks, Paolo.
>
> /////////////////////////
>
OK.
Jason
prev parent reply other threads:[~2019-09-09 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 14:28 Paolo Carlini
2019-09-09 8:24 ` [C++ Patch ping] " Paolo Carlini
2019-09-09 21:01 ` 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=6ababa8d-4eca-dd6a-c8e2-313918687751@redhat.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).