From: Alan Modra <amodra@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: x86: remove i386-opc.c
Date: Thu, 22 Dec 2022 20:13:03 +1030 [thread overview]
Message-ID: <Y6Qmp43kLj1EUtdX@squeak.grove.modra.org> (raw)
In-Reply-To: <e461f075-67fa-d1b8-c8de-a8ad22ab62a6@suse.com>
On Thu, Dec 22, 2022 at 09:49:41AM +0100, Jan Beulich wrote:
> On 20.12.2022 12:39, Alan Modra wrote:
> > On Tue, Dec 20, 2022 at 09:40:14AM +0100, Jan Beulich wrote:
> >> On 20.12.2022 09:33, Alan Modra via Binutils wrote:
> >>> Regen opcodes/po/POTFILES.in
> >>>
> >>> diff --git a/opcodes/po/POTFILES.in b/opcodes/po/POTFILES.in
> >>> index 9906bf14848..effd73f8f78 100644
> >>> --- a/opcodes/po/POTFILES.in
> >>> +++ b/opcodes/po/POTFILES.in
> >>> @@ -73,7 +73,6 @@ h8300-dis.c
> >>> hppa-dis.c
> >>> i386-dis.c
> >>> i386-gen.c
> >>> -i386-opc.c
> >>> i386-opc.h
> >>> ia64-asmtab.c
> >>> ia64-asmtab.h
> >>
> >> Which makes me wonder: If this is the list of files where string literals
> >> may/will need translation, are files like i386-gen.c (i.e. build time
> >> helper tool sources) really supposed to be enumerated here?
> >
> > Probably not, but the build time tools don't tend to use gettext and
> > thus all it does is slow down generation of .pot files a little.
>
> Irrespective of them using gettext (I've now queued a patch to remove
> that from i386-gen.c), wouldn't it make sense to convert
>
> POTFILES = $(HFILES) $(CFILES)
>
> to
>
> POTFILES = $(HFILES) $(LIBOPCODES_CFILES)
>
> thus eliminating translation for build time tools regardless? At which
> point the question would be whether CFILES as a variable needs retaining.
> Afaics the definition of POTFILES is the only user.
Sounds reasonable to me.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2022-12-22 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 8:33 Alan Modra
2022-12-20 8:40 ` Jan Beulich
2022-12-20 11:39 ` Alan Modra
2022-12-20 11:44 ` Jan Beulich
2022-12-21 17:51 ` H.J. Lu
2022-12-22 8:49 ` Jan Beulich
2022-12-22 9:43 ` Alan Modra [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=Y6Qmp43kLj1EUtdX@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).