public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jonathan Yong <10walls@gmail.com>
To: cygwin@cygwin.com
Cc: Stromeko@NexGo.DE
Subject: Re: libgccjit
Date: Thu, 11 Mar 2021 16:00:47 +0000	[thread overview]
Message-ID: <629c22b5-9c89-51dd-57a1-13af6b0a87df@gmail.com> (raw)
In-Reply-To: <YEnuDNuBo1mVcaZs@calimero.vinschen.de>


[-- Attachment #1.1.1: Type: text/plain, Size: 434 bytes --]

On 3/11/21 10:16 AM, Corinna Vinschen wrote:
> On Mar 10 12:00, Ken Brown via Cygwin wrote:
>> Emacs development (on the feature/native-comp branch) is using libgccjit.
>> Is it possible to build this library on Cygwin?
> 
> Isn't this a question for Jon?  I CCed him.
> 
> 
> Corinna
> 

I've not honestly tried setting up libgccjit, looks like its as simple 
as adding jit to --enable-languages.

Achim, mind trying?

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 8035 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2021-03-11 16:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 17:00 libgccjit Ken Brown
2021-03-11 10:16 ` libgccjit Corinna Vinschen
2021-03-11 16:00   ` Jonathan Yong [this message]
2021-03-13 20:28     ` libgccjit Achim Gratz
2021-03-14  6:52       ` libgccjit Achim Gratz
2021-03-14 14:54         ` libgccjit Jonathan Yong
2021-03-14 16:24           ` libgccjit Achim Gratz
2021-03-14 19:06             ` libgccjit Andy Moreton
2021-03-14 20:22               ` libgccjit Achim Gratz
2021-03-14 21:19                 ` libgccjit Andy Moreton
2021-03-14 20:42             ` libgccjit Achim Gratz
2021-03-11 17:19   ` libgccjit Achim Gratz
2021-04-04 19:45 ` libgccjit Achim Gratz
2021-04-04 20:39   ` libgccjit Ken Brown
2021-04-05 19:01   ` libgccjit Achim Gratz

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=629c22b5-9c89-51dd-57a1-13af6b0a87df@gmail.com \
    --to=10walls@gmail.com \
    --cc=Stromeko@NexGo.DE \
    --cc=cygwin@cygwin.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).