From: Jason Merrill <jason@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [Patch] add more C++ name hints. v2
Date: Tue, 30 Aug 2022 09:32:01 -0400 [thread overview]
Message-ID: <75dcc9dd-5b82-c999-7d9f-294737432f2a@redhat.com> (raw)
In-Reply-To: <CAP3s5k_h6j+KHeiWM9cTPyBUSNgJJ+r7UAQr+MH-0jGUVn0jDw@mail.gmail.com>
On 8/22/22 15:09, Ulrich Drepper via Gcc-patches wrote:
> This is the second version of the proposed patch to add more identifiers to
> the known list to give hints about #include and version numbers.
>
> Marek looked through the first version and found it acceptable but remarked
> that the list is getting long and the sequential search performed by the
> current code might not be adequate. Especially because I offered to add
> even more known names to the list.
>
> This second version replaces the current lookup implementation with a
> gperf-generated hash function. Since gperf is already a dependency for
> maintainers the use of the tool itself shouldn't be a problem.
>
> I followed the existing practice for the cfns.gperf file and its use so, if
> the handling of that file works, so should the handling of the new file,
> std-name-hint.gperf.
>
> Please let me know if this is acceptable. I built a compiler with this
> code and tested the hinting.
OK, thanks.
> contrib/ChangeLog
> * gcc_update (files_and_dependencies): Add gcc/cp/std-name-hint.h
> depend on gcc/cp/std-name-hint.gperf.
>
> gcc/cp/ChangeLog
> * Make-lang.in: Add rule to build std-name-hint.h.
> * name-lookup.cc (struct std_name_hint): Remove definition.
> Instead...
> Include "std-name-hint.h".
> (get_std_name_hint): Remove hints array and lookup code. Instead
> call
> std_name_hint_lookup::find.
> * std-name-hint.gperf: New file.
> * std-name-hint.h: New file.
prev parent reply other threads:[~2022-08-30 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 19:09 Ulrich Drepper
2022-08-30 10:58 ` Ulrich Drepper
2022-08-30 10:58 ` Ulrich Drepper
2022-08-30 13:32 ` 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=75dcc9dd-5b82-c999-7d9f-294737432f2a@redhat.com \
--to=jason@redhat.com \
--cc=drepper@redhat.com \
--cc=gcc-patches@gcc.gnu.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).