From: Alan Modra <amodra@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: Alan Modra via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: sim regen
Date: Sat, 19 Aug 2023 09:16:15 +0930 [thread overview]
Message-ID: <ZOACx3KJaUO2ziZb@squeak.grove.modra.org> (raw)
In-Reply-To: <87y1i8wbg9.fsf@tromey.com>
On Fri, Aug 18, 2023 at 10:40:38AM -0600, Tom Tromey wrote:
> >>>>> "Alan" == Alan Modra via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Alan> The attached patch regenerates sim files.
> Alan> Tested with the following tools from a recent binutils build in
> Alan> sim-site-config.exp, plus a few cross compilers.
>
> I didn't really look at the patch. I think regeneration like this
> should be fine.
>
> I'm curious how you did it. cgen does not run for me. I suspect maybe
> you used an old version of Guile, but confirmation would be nice.
I'm using guile 1.8.8, built from source five years ago. I can't
remember why I built it, possibly because the cgen README says "CGEN
has been tested with Guile 1.4.1, 1.6.8, and 1.8.5." and likely I also
found cgen didn't work with cgen 2 or later. cgen is current master
branch sourceware git/cgen.git.
Besides the "sim regen preparation" patch which you OK'd, I also have
"sim prune warnings"
https://sourceware.org/pipermail/gdb-patches/2023-August/201586.html
and "sim --enable-cgen-maint"
https://sourceware.org/pipermail/gdb-patches/2023-August/201494.html
in my tree.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2023-08-18 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 13:39 Alan Modra
2023-08-18 16:40 ` Tom Tromey
2023-08-18 23:46 ` Alan Modra [this message]
2023-08-19 0:26 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 11:59 Alan Modra
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=ZOACx3KJaUO2ziZb@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).