From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 74805@debbugs.gnu.org, rb@ravenbrook.com
Subject: bug#74805: 30.0.92; Trying to build scratch/igc on Cygwin
Date: Sat, 21 Dec 2024 09:24:22 +0200 [thread overview]
Message-ID: <86v7vd8pnd.fsf@gnu.org> (raw)
In-Reply-To: <d5965019-4bd6-419a-8b45-829b6d9c9ee5@cornell.edu> (message from Ken Brown on Fri, 20 Dec 2024 18:48:37 -0500)
> Date: Fri, 20 Dec 2024 18:48:37 -0500
> Cc: 74805@debbugs.gnu.org, Richard Brooksby <rb@ravenbrook.com>
> From: Ken Brown <kbrown@cornell.edu>
>
> This is an update on my attempts to port the MPS to Cygwin and build the
> scratch/igc branch. The GitHub repo that I cited above now consists of
> 4 branches:
>
> 1. The "master" branch is an MPS fork with README.Cygwin added. This
> file explains in detail what I'm summarizing here.
>
> 2. The "w3" branch attempts to use the Windows interface on Cygwin. For
> example, it uses direct calls to VirtualAlloc instead of Cygwin's mmap.
> This attempt fails because it's not compatible with Cygwin's fork.
>
> 3. The "mmap" branch is a straightforward port, mostly imitating the
> FreeBSD port. It currently (with Cygwin 3.5.5) fails because of a
> limitation of Cygwin's mmap. But I have a simple patch to Cygwin in the
> works that removes that limitation. With that patch, 37 of the 38 MPS
> tests pass. I still need to debug the failing test. I'm cautiously
> optimistic that I can get this approach to work. Either way, I expect
> the Cygwin patch to soon be available in a test release of Cygwin 3.6.0
> so that other Cygwin users can try it.
>
> 4. The "generic" branch uses generic implementations of some of the MPS
> features. For example, it uses malloc instead of mmap. This passes all
> of the MPS tests, and Emacs seems to work well so far in limited
> testing. I suspect that there may be some performance problems, but I
> haven't seen them yet.
>
> Once I've determined whether or not the mmap approach will work, I'll
> post the MPS patches here either for the mmap branch or the generic branch.
Thanks for the update, I think this is very good news.
next prev parent reply other threads:[~2024-12-21 7:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 22:50 bug#74805: 30.0.92; Trying to build scratch/igc on Cygwin Ken Brown
2024-12-11 23:47 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-12 18:14 ` Ken Brown
2024-12-11 23:57 ` Andrea Corallo
2024-12-12 6:09 ` Eli Zaretskii
2024-12-12 18:12 ` Ken Brown
2024-12-12 19:25 ` Eli Zaretskii
2024-12-12 23:17 ` Stefan Kangas
2024-12-13 7:51 ` Eli Zaretskii
2024-12-20 23:48 ` Ken Brown
2024-12-21 7:24 ` Eli Zaretskii [this message]
2024-12-12 11:05 ` Stefan Kangas
2024-12-12 11:30 ` Eli Zaretskii
2024-12-12 12:06 ` Gerd Möllmann
2024-12-12 14:38 ` Eli Zaretskii
2024-12-12 15:01 ` Gerd Möllmann
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86v7vd8pnd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74805@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
--cc=rb@ravenbrook.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).