From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [PATCH] attribs: Use existing traits for excl_hash_traits
Date: Fri, 10 Nov 2023 13:28:38 -0700 [thread overview]
Message-ID: <99d40fd7-41fb-4321-b065-2afc2f52959a@gmail.com> (raw)
In-Reply-To: <mpth6lzawpw.fsf@arm.com>
On 11/6/23 05:32, Richard Sandiford wrote:
> Ping.
>
> Richard Sandiford via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
>> excl_hash_traits can be defined more simply by reusing existing traits.
>>
>> Tested on aarch64-linux-gnu. OK to install?
>>
>> Richard
>>
>>
>> gcc/
>> * attribs.cc (excl_hash_traits): Delete.
>> (test_attribute_exclusions): Use pair_hash and nofree_string_hash
>> instead.
OK. Sorry this fell through the cracks.
jeff
prev parent reply other threads:[~2023-11-10 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 15:40 Richard Sandiford
2023-11-06 12:32 ` Richard Sandiford
2023-11-10 20:28 ` Jeff Law [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=99d40fd7-41fb-4321-b065-2afc2f52959a@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).