public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Jose E. Marchesi" <jemarch@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: cgen@sourceware.org
Subject: Re: [RFC 00/14] Port to Guile 3.0
Date: Sun, 20 Aug 2023 10:03:17 +0200	[thread overview]
Message-ID: <87cyzirvi2.fsf@gnu.org> (raw)
In-Reply-To: <20230819174900.866436-1-tom@tromey.com> (Tom Tromey's message of "Sat, 19 Aug 2023 11:41:59 -0600")


Hi Tom.

> I tried re-running cgen this week and was surprised to find it didn't
> work with any version of Guile that I had available.  Apparently it
> works with the long-since-obsolete Guile 1.8, and nothing newer.
>
> This series is my attempt at a port, with random other cleanups mixed
> in.

Thank you so much for doing this.  It is a very welcome change.  It
sucks to install guile 1.8 locally in order to use CGEN.

> Note that Guile 2.x also doesn't really seem to work -- it was very
> slow and never completed.  I got impatient, so I'm not sure if it
> would have eventually, or if there is some bug.
>
> I didn't try Guile 1.8 but I would assume it no longer works after
> this series.

I don't think that is a problem.

Guile 3.0 was released more than three years ago, it is available in
Fedora 35 and later, FreeBSD, OpenBSD, Guix, NixPkg stable, Mageia, SUSE
Tumbleweed, Parabola, Slackware current, Ubuntu 20 or later, Debian
stable.

> The Guile compiler cannot be used due to the loading approach taken in
> cgen.  This can be fixed but it is a somewhat larger effort, either
> involving real modules or the use of the slib require/provide system.
>
> Another possible change would be removing cos.scm in favor of Guile's
> built-in object system.  Patch #10 is basically a hack to work around
> a problem with the custom object system.  It can probably be fixed in
> a better way, but I didn't bother.
>
> I rebuilt all the cgen code in binutils-gdb with this patch after
> Alan's recent regeneration, and verified there are no changes.
>
> Tom

  parent reply	other threads:[~2023-08-20  8:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-19 17:41 Tom Tromey
2023-08-19 17:42 ` [RFC 01/14] Add a .gitignore Tom Tromey
2023-08-20  8:04   ` Jose E. Marchesi
2023-08-19 17:42 ` [RFC 02/14] Remove some 'fastcall' code Tom Tromey
2023-08-20  8:13   ` Jose E. Marchesi
2023-08-22 16:52     ` Tom Tromey
2023-08-19 17:42 ` [RFC 03/14] Remove bound-symbol? Tom Tromey
2023-08-20  8:14   ` Jose E. Marchesi
2023-08-19 17:42 ` [RFC 04/14] Remove =? and >=? aliases Tom Tromey
2023-08-20  8:15   ` Jose E. Marchesi
2023-08-19 17:42 ` [RFC 05/14] Fix bug in insn.scm Tom Tromey
2023-08-20  8:15   ` Jose E. Marchesi
2023-08-19 17:42 ` [RFC 06/14] Remove support for old versions of Guile Tom Tromey
2023-08-19 17:42 ` [RFC 07/14] Use define-macro in rtl.scm Tom Tromey
2023-08-19 17:42 ` [RFC 08/14] Remove let bindings of macros Tom Tromey
2023-08-20  8:33   ` Jose E. Marchesi
2023-08-19 17:42 ` [RFC 09/14] Remove define-in-define Tom Tromey
2023-08-19 17:42 ` [RFC 10/14] Hack cos.scm to work with new Guile Tom Tromey
2023-08-19 17:42 ` [RFC 11/14] Invalid code in rtx-traverse.scm Tom Tromey
2023-08-20  8:42   ` Jose E. Marchesi
2023-08-19 17:42 ` [RFC 12/14] Nuke cgen-call-with-debugging and cgen-debugging-stack-start Tom Tromey
2023-08-19 17:42 ` [RFC 13/14] Load macros before uses Tom Tromey
2023-08-19 17:42 ` [RFC 14/14] Remove pprint.scm and cos-pprint.scm Tom Tromey
2023-08-20  8:03 ` Jose E. Marchesi [this message]
2023-08-20 17:26   ` [RFC 00/14] Port to Guile 3.0 Frank Ch. Eigler
2023-08-20 19:52     ` Tom Tromey
2023-08-21  1:38       ` Frank Ch. Eigler
2023-08-21 13:06 ` Julian Brown

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=87cyzirvi2.fsf@gnu.org \
    --to=jemarch@gnu.org \
    --cc=cgen@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).