From: Richard Sandiford <richard.sandiford@arm.com>
To: Mikhail Maltsev <maltsevm@gmail.com>
Cc: gcc-patches <gcc-patches@gnu.org>,
Richard Henderson <rth@redhat.com>,
Trevor Saunders <tbsaunde@tbsaunde.org>
Subject: Re: [PATCH] Move gen_* stubs from defaults.h to genflags
Date: Wed, 10 Jun 2015 07:44:00 -0000 [thread overview]
Message-ID: <87r3pkvxwo.fsf@e105548-lin.cambridge.arm.com> (raw)
In-Reply-To: <87vbewvyac.fsf@e105548-lin.cambridge.arm.com> (Richard Sandiford's message of "Wed, 10 Jun 2015 08:05:15 +0100")
Richard Sandiford <richard.sandiford@arm.com> writes:
> There again, this is a generator, so those kinds of concerns aren't
> particularly important. If we do keep the above though, I think we
> should put the hasher in hash-map-table.h now.
Of course I mean hash-map-traits.h :-)
next prev parent reply other threads:[~2015-06-10 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 6:06 Mikhail Maltsev
2015-06-10 7:12 ` Richard Sandiford
2015-06-10 7:44 ` Richard Sandiford [this message]
2015-06-14 23:41 ` Mikhail Maltsev
2015-06-15 9:38 ` Richard Sandiford
2015-06-10 15:08 ` Trevor Saunders
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=87r3pkvxwo.fsf@e105548-lin.cambridge.arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gnu.org \
--cc=maltsevm@gmail.com \
--cc=rth@redhat.com \
--cc=tbsaunde@tbsaunde.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).