From: Jason Merrill <jason@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Andreas Schwab <schwab@suse.de>,
gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH for c++/81073, constexpr and static var in statement-expression
Date: Wed, 21 Jun 2017 14:52:00 -0000 [thread overview]
Message-ID: <CADzB+2nC8DXqsBvpFdEdKFxbGELX0Z6VNa5Ufrb3CPNJNW5hxA@mail.gmail.com> (raw)
In-Reply-To: <20170621103235.GO2123@tucnak>
On Wed, Jun 21, 2017 at 6:32 AM, Jakub Jelinek <jakub@redhat.com> wrote:
> The following patch fixes it by allowing that wording too on the line 10.
> Is this ok for trunk or do you have some other preference?
OK, thanks.
Jason
prev parent reply other threads:[~2017-06-21 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 17:42 Jason Merrill
2017-06-20 9:40 ` Andreas Schwab
2017-06-20 18:50 ` Jason Merrill
2017-06-20 19:45 ` Andreas Schwab
2017-06-21 10:32 ` Jakub Jelinek
2017-06-21 14:52 ` 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+2nC8DXqsBvpFdEdKFxbGELX0Z6VNa5Ufrb3CPNJNW5hxA@mail.gmail.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=schwab@suse.de \
/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).