From: Jason Merrill <jason@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] introduce C++ API data base and generator for C++ hints
Date: Wed, 19 Oct 2022 15:09:22 -0400 [thread overview]
Message-ID: <7b38ad88-4777-2bc7-0217-bb525f995180@redhat.com> (raw)
In-Reply-To: <CAP3s5k8fE+_zFjwrbjQ19a0nwvC_yVBz5wo=HyaqcDCZt+NvPw@mail.gmail.com>
On 10/18/22 11:06, Ulrich Drepper wrote:
> I updated the patch based on the feedback from Jason and Martin. It
> keeps the CSV file and the python script in the cp/ directory. There
> also is still only one Python script.
>
> If there is agreement that either of those should change despite the
> arguments I gave in the reply to Jason's email I'll change it.
> Otherwise I think the patch is ready to be applied.
>
> There should be no change for the non-developer, I've adjusted the
> Makefile so that no file is generated based on time stamps unless the
> maintainer mode is selected.
>
> I added the comment about the shared ownership only to the CSV file, not
> the Python script. The latter shouldn't need frequent updates and
> therefore the issue is less critical.
>
> OK?
OK.
> 2022-10-18 Jonathan Wakely <jwakely@redhat.com
> <mailto:jwakely@redhat.com>>
> Ulrich Drepper <drepper@redhat.com
> <mailto:drepper@redhat.com>>
>
> contrib/
> * gcc_update: Add rule for gcc/cp/std-name-hint.gperf.
>
> gcc/cp/
> * Make-lang.in: Add rules to generate std-name-hint.gperf. Adjust
> rule to generate std-name-hint.h to allow chain rule.
> * std-name-hint.h: Regenerated.
> * std-name-hint.gperf: This file is now generated.
> * cxxapi-data-.csv: New file. CSV file with C++ API data.
> * gen-cxxapi-file.py: New file. Generate std-name-hint.gperf
> and module export source (in future).
>
prev parent reply other threads:[~2022-10-19 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:06 Ulrich Drepper
2022-10-19 19:09 ` 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=7b38ad88-4777-2bc7-0217-bb525f995180@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).