From: Christophe Lyon <christophe.lyon@linaro.org>
To: Jens Remus <jremus@linux.ibm.com>
Cc: Simon Marchi <simark@simark.ca>,
binutils@sourceware.org, gdb@sourceware.org,
GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: [RFC] add regenerate Makefile target
Date: Wed, 27 Mar 2024 19:14:53 +0100 [thread overview]
Message-ID: <CAPS5khZbQQsFQ7zq+8O57jE9+ZvB52evuQBebM8HaQ8iJv=H1w@mail.gmail.com> (raw)
In-Reply-To: <78f1d113-f8ac-4a76-8dea-9f92519c1a89@linux.ibm.com>
On Tue, 26 Mar 2024 at 16:42, Jens Remus <jremus@linux.ibm.com> wrote:
>
> Am 15.03.2024 um 09:50 schrieb Christophe Lyon:
> > On Thu, 14 Mar 2024 at 19:10, Simon Marchi <simark@simark.ca> wrote:
> >> On 2024-03-13 04:02, Christophe Lyon via Gdb wrote:
> ...
> >> There's just the issue of files that are generated using tools that are
> >> compiled. When experimenting with maintainer mode the other day, I
> >> stumbled on the opcodes/i386-gen, for instance. I don't have a good
> >> solution to that, except to rewrite these tools in a scripting language
> >> like Python.
> >
> > So for opcodes, it currently means rewriting such programs for i386,
> > aarch64, ia64 and luckily msp430/rl78/rx share the same opc2c
> > generator.
> > Not sure how to find volunteers?
>
> Why are those generated source files checked into the repository and not
> generated at build-time? Would there be a reason for s390 do so as well
> (opcodes/s390-opc.tab is generated at build-time from
> opcodes/s390-opc.txt using s390-mkopc built from opcodes/s390-mkopc.c)?
>
I remember someone mentioned a requirement of being able to rebuild
with the sources on a read-only filesystem.
I don't know if there's a requirement that such generated files should
be part of the source tree though. Is opcodes/s390-opc.tab in builddir
or in srcdir?
I think there are other motivations but I can't remember them at the moment :-)
Thanks,
Christophe
> Thanks and regards,
> Jens
> --
> Jens Remus
> Linux on Z Development (D3303) and z/VSE Support
> +49-7031-16-1128 Office
> jremus@de.ibm.com
>
> IBM
>
> IBM Deutschland Research & Development GmbH; Vorsitzender des
> Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der
> Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294
> IBM Data Privacy Statement: https://www.ibm.com/privacy/
next prev parent reply other threads:[~2024-03-27 18:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 8:02 Christophe Lyon
2024-03-14 18:10 ` Simon Marchi
2024-03-15 8:50 ` Christophe Lyon
2024-03-15 14:13 ` Eric Gallager
2024-03-15 14:25 ` Tom Tromey
2024-03-16 17:30 ` Simon Marchi
2024-03-18 17:28 ` Christophe Lyon
2024-03-20 15:11 ` Simon Marchi
2024-03-18 16:13 ` Christophe Lyon
2024-03-16 17:16 ` Simon Marchi
2024-03-18 17:25 ` Christophe Lyon
2024-03-19 17:11 ` Christophe Lyon
2024-03-19 18:03 ` Tom Tromey
2024-03-20 12:05 ` Eric Gallager
2024-03-20 15:34 ` Simon Marchi
2024-03-21 14:32 ` Christophe Lyon
2024-03-25 14:19 ` Christophe Lyon
2024-03-27 18:22 ` Christophe Lyon
2024-04-08 9:22 ` Christophe Lyon
[not found] ` <78f1d113-f8ac-4a76-8dea-9f92519c1a89@linux.ibm.com>
2024-03-27 18:14 ` Christophe Lyon [this message]
2024-03-28 8:55 ` Jens Remus
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='CAPS5khZbQQsFQ7zq+8O57jE9+ZvB52evuQBebM8HaQ8iJv=H1w@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jremus@linux.ibm.com \
--cc=simark@simark.ca \
/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).