From: Andrea Corallo <akrl@sdf.org>
To: jit@gcc.gnu.org
Subject: Re: Libgccjit Windows compatibility
Date: Wed, 01 Jan 2020 00:00:00 -0000 [thread overview]
Message-ID: <xjfmu96uz6v.fsf@sdf.org> (raw)
In-Reply-To: <xjf8smwsnnl.fsf@sdf.org> (Andrea Corallo's message of "Sat, 28 Dec 2019 11:19:26 +0000")
Andrea Corallo <akrl@sdf.org> writes:
> Hi all,
>
> In my spare time I've been working on a project to give Emacs the
> ability of compiling Elisp. This is libgccjit based.
>
> On emacs-devel the discussion is ongoing and the question has been
> raised about Windows compatibility. Question for which I've no answer.
>
> About this I've just found this old thread.
>
> https://gcc.gnu.org/ml/jit/2015-q3/msg00124.html
>
> I wanted to ask if we are aware of fundamental problems preventing a
> Windows port or this was just never completed and up-streamed.
>
> Bests
> Andrea
Hi all,
Just for the record, yesterday I bumped into this Chinese blog where the
guy hacked a libgccjit on Windows 10 using mingw64 to run the Emacs
native-comp branch.
http://www.albertzhou.net/blog/2020/01/emacs-native-comp.html
I think this answer my original question a perhaps could help somebody
wanting to attempt such a port.
Andrea
--
akrl@sdf.org
prev parent reply other threads:[~2020-02-25 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Andrea Corallo
2020-01-01 0:00 ` Andrea Corallo [this message]
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=xjfmu96uz6v.fsf@sdf.org \
--to=akrl@sdf.org \
--cc=jit@gcc.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).