From: Jakub Jelinek <jakub@redhat.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: Jason Merrill <jason@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [C++ PATCH] Further get_identifier ("string literal") C++ FE caching
Date: Wed, 18 Jul 2018 22:43:00 -0000 [thread overview]
Message-ID: <20180718224308.GJ7166@tucnak> (raw)
In-Reply-To: <5b4fb878.1c69fb81.7fe02.d72a@mx.google.com>
On Wed, Jul 18, 2018 at 06:00:20PM -0400, Nathan Sidwell wrote:
> So cool! Thanks.
Ok for both patches or just this one?
Jakub
next prev parent reply other threads:[~2018-07-18 22:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-13 13:49 C++ patch ping Jakub Jelinek
2018-07-13 16:24 ` Nathan Sidwell
2018-07-13 16:53 ` Jakub Jelinek
2018-07-18 10:19 ` [C++ PATCH] Hide __for_{range,begin,end} symbols (PR c++/85515, take 2) Jakub Jelinek
2018-07-18 21:05 ` [C++ PATCH] Further get_identifier ("string literal") C++ FE caching Jakub Jelinek
2018-07-18 22:00 ` Nathan Sidwell
2018-07-18 22:43 ` Jakub Jelinek [this message]
2018-07-25 16:40 ` Nathan Sidwell
2018-07-13 16:42 ` C++ patch ping Nathan Sidwell
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=20180718224308.GJ7166@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=nathan@acm.org \
/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).