From: Nathan Sidwell <nathan@acm.org>
To: Andreas Schwab <schwab@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ PATCH] namespace bindings
Date: Mon, 08 May 2017 13:14:00 -0000 [thread overview]
Message-ID: <18c5c20f-a612-ed3e-6f55-db85845e4255@acm.org> (raw)
In-Reply-To: <mvma86ntuvu.fsf@suse.de>
On 05/08/2017 08:07 AM, Andreas Schwab wrote:
> On Mai 05 2017, Nathan Sidwell <nathan@acm.org> wrote:
>
>> This cleanup patch kills IDENTIFIER_NAMESPACE_VALUE and replaces
>> {get,set}_namespace_binding with get_namespace_value and set_global_value
>> respectively.
>
> I'm getting this regression on ia64:
Sorry, I'll take a look ...
--
Nathan Sidwell
next prev parent reply other threads:[~2017-05-08 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 20:25 Nathan Sidwell
2017-05-08 12:41 ` Andreas Schwab
2017-05-08 13:14 ` Nathan Sidwell [this message]
2017-05-08 14:33 ` Nathan Sidwell
2017-05-08 15:25 ` Andreas Schwab
2017-05-08 17:03 ` Nathan Sidwell
2017-05-08 13:06 ` Jason Merrill via gcc-patches
2017-05-08 13:34 ` Nathan Sidwell
2017-05-08 15:54 ` Nathan Sidwell
2017-05-23 19:47 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=18c5c20f-a612-ed3e-6f55-db85845e4255@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--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).