unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Robin Templeton <robin@terpri.org>
To: guile-devel@gnu.org
Subject: Re: Guile 3 and wip-elisp/Emacs
Date: Wed, 20 Oct 2021 07:43:06 -0400	[thread overview]
Message-ID: <87ee8fncqd.fsf@terpri.org> (raw)
In-Reply-To: 45-613b7600-3-2694eb00@100567081

"Gregg Sangster" <gregg@thesangsters.ca> writes:

> Hello Guile Hackers,
>
> I've rebased the wip-elisp branch on top of commit
> 449f50dd84a081aea16ef678e32bf37abe429ff6 (git describe:
> v3.0.4-64-g33232cb5c4).  It's published here:
>
> https://git.sr.ht/~g20r/guile

This is wonderful, thank you! (IIUC, Christine and Ricardo wrote
ChangeLog entries and did some rebasing, but I don't think it's been
fully rebased for some time, so this is a big step forward!)

N.B. The commit messages need minor rewording, so this will require
trivial changes before merging even if's otherwise perfect.

> There are two additional failed tests which appear to be new tests
> added since the last work on the wip-elisp branch.  Also, ./configure
> requires the --disable-jit option as the build fails otherwise.  I
> have not yet investigated any of these issues.

Christine noted some "questionable" compiler changes, where my changes
might conflict with Andy's, so this isn't surprising but it's useful to
have potential confirmation. The elisp changes were fairly simple, so it
shouldn't be too difficult to fix, if that is indeed the problem.

> I don't have much experience with Guile itself or the Guile codebase.
> The next commit has a conflict I was not able to resolve: that's why
> it's not rebased all the way up to the tip of main.  My next tasks are
> to get the current Guile Emacs running on this version of Guile
> followed by fixing the JIT build failure, rebasing this to the tip of
> main and rebasing Guile Emacs on a more recent Emacs (I believe it is
> currently v24.something).

Rebasing onto a somewhat newer Emacs should be pretty straightforword,
and certainly worthwhile on its on. However, rebasing onto emacs master
is a major task that'll probably take several person-months of fairly
tedious work...

> My question is if this is worthwhile work?  I don't have much time to
> spend on it but am happy to keep hacking away if there's still
> upstream interest.

From my perspective, it certainly is! There is plenty of interest from
the Guile side AFAICT; the Emacs maintainers have been (understandably)
skeptical about the project in general, but if we can make it correct
*and* fast I think they'll be more interested, especially if Guile 3's
JIT outperforms emacs native-comp in practice.

Thanks,
Robin

-- 
<robin> "Digital Imperialism: The Highest Stage of Computing Capitalism"
<dsk>   -- the Lenin of Emacs




  parent reply	other threads:[~2021-10-20 11:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 15:12 Guile 3 and wip-elisp/Emacs Gregg Sangster
2021-09-10 19:59 ` Dr. Arne Babenhauserheide
2021-09-13  2:13   ` Christine Lemmer-Webber
2021-10-14 14:01     ` Gregg Sangster
2021-10-14 17:34       ` Ricardo Wurmus
2021-10-20 10:56         ` Gregg Sangster
2021-10-21 14:05           ` Ricardo Wurmus
2021-10-21 17:49       ` Robin Templeton
2021-10-20 11:59   ` Robin Templeton
2021-09-13 10:56 ` Ricardo Wurmus
2021-09-20 10:39   ` Gerry Agbobada
2021-10-14 13:35   ` Gregg Sangster
2021-10-16  5:25     ` Christine Lemmer-Webber
2021-10-19 21:59       ` Christine Lemmer-Webber
2021-10-19 22:29         ` Ludovic Courtès
2021-10-20  1:46           ` Christine Lemmer-Webber
2021-10-20  2:51             ` Christine Lemmer-Webber
2021-10-20 16:27             ` Christopher Allan Webber
2021-10-22 16:11               ` Christine Lemmer-Webber
2021-10-22 16:17                 ` Christine Lemmer-Webber
2021-10-22 18:38                   ` Gregg Sangster
2021-10-21 19:34             ` Robin Templeton
2021-10-22  2:59               ` Christine Lemmer-Webber
2021-10-20 10:43         ` Gregg Sangster
2021-10-20 11:43 ` Robin Templeton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-10 15:09 Gregg Sangster
2021-09-10 15:09 Gregg Sangster

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ee8fncqd.fsf@terpri.org \
    --to=robin@terpri.org \
    --cc=guile-devel@gnu.org \
    /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).