From: Jan Beulich <jbeulich@suse.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] x86: Remove libopcodes dependency
Date: Wed, 23 Nov 2022 09:36:13 +0100 [thread overview]
Message-ID: <4d995c45-7e4c-4f66-5459-1b1c33aa4dd8@suse.com> (raw)
In-Reply-To: <20221122181927.251937-1-hjl.tools@gmail.com>
On 22.11.2022 19:19, H.J. Lu wrote:
> --- a/gas/Makefile.am
> +++ b/gas/Makefile.am
> @@ -446,6 +446,12 @@ development.exp: $(BFDDIR)/development.sh
> $(EGREP) "(development|experimental)=" $(BFDDIR)/development.sh \
> | $(AWK) -F= '{ print "set " $$1 " " $$2 }' > $@
>
> +$(srcdir)/../opcodes/i386-init.h $(srcdir)/../opcodes/i386-tbl.h: \
> + @MAINT@ $(srcdir)/../opcodes/i386-opc.tbl \
> + $(srcdir)/../opcodes/i386-reg.tbl \
> + $(srcdir)/../opcodes/i386-opc.h
> + cd ../opcodes; make gen-i386-tbl
This recursing into a different directory (and then even using "cd" and
"make" instead of "$(MAKE) -C") is what I have specifically avoided in
my patches. This is deemed an anti-pattern by many people: If you
consider running make in just gas/ is an okay thing to do, then running
make in just opcodes/ is, too. Yet with such a rule doing so in parallel
can result in strange collisions and likely partially broken files.
Therefore with my general maintainer hat on I object to such an approach.
If you really want to generate the files from gas/, then you should do
so there, i.e. also going as far as building i386-gen there. Once
again I did consider doing to, but deemed it awkward: Even if we don't
use libopcodes.{a,so} anymore, I think the opcode table processing
would better remain in opcodes/ - we'd use that library no longer as
a binary but as a (generated) source code one. If you think differently,
I wouldn't object to you following this alternative approach.
As a formal remark: In the description I would expect to be credited at
least for recognizing the opportunity; really you've re-used some of
what I've had in my patches, irrespective of you perhaps having done
things from scratch (and having spotted/corrected an oversight of mine,
which I was about to submit v3 of my series for, but which now I will
wait with until the above is settled - sadly meaning yet further delays
for the growing pile of other work I have pending on top).
Jan
next prev parent reply other threads:[~2022-11-23 8:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 18:19 H.J. Lu
2022-11-23 8:36 ` Jan Beulich [this message]
2022-11-28 23:43 ` H.J. Lu
2022-11-29 9:12 ` Jan Beulich
2022-11-24 10:19 ` Jan Beulich
2022-11-28 23:49 ` [PATCH v2] " H.J. Lu
2022-11-29 9:22 ` Jan Beulich
2022-11-29 19:38 ` H.J. Lu
2022-11-30 0:06 ` H.J. Lu
2022-11-30 6:58 ` Jan Beulich
2022-11-30 22:22 ` H.J. Lu
2022-12-01 7:41 ` Jan Beulich
2022-12-01 18:26 ` [PATCH v3] " H.J. Lu
2022-12-02 7:16 ` Jan Beulich
2022-12-02 17:19 ` H.J. Lu
2022-12-05 11:25 ` Jan Beulich
2022-11-30 7:31 ` [PATCH v2] " Jan Beulich
2022-11-30 22:15 ` H.J. Lu
2022-12-01 7:21 ` Jan Beulich
2022-12-01 18:20 ` H.J. Lu
2022-12-02 7:10 ` Jan Beulich
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=4d995c45-7e4c-4f66-5459-1b1c33aa4dd8@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).