From: Basile Starynkevitch <basile@starynkevitch.net>
To: jit@gcc.gnu.org
Subject: Re: existing C frontend for libgccjit?
Date: Sat, 7 Oct 2023 16:47:29 +0200 [thread overview]
Message-ID: <dd29f59b-c08a-4cfa-910b-182cdce56cc1@starynkevitch.net> (raw)
In-Reply-To: <xUyN-um9ScbmLylXsJiiBi5lDN-EqVJrG7l2Twf_EURFKAXh5KnTSwEbYNjnZEtTaeET3RoMqTTeDsMkz3TnQJMSFJt93gcmVQolubmOUnM=@zhuyi.fan>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On 10/7/23 16:43, Schrodinger ZHU Yifan wrote:
> Hi,
>
> In my case, I wanted to include inline definitions in a header file
> into a context. Is there a way to this without writing all the functions?
I don't know about it.
An alternative (generating *less efficient* code) could be to consider
using GNU lightning. https://www.gnu.org/software/lightning/
GNU lightning generates "unoptimized" code, but it generates it faster
than libgccjit.
Another alternative could be to develop your GCC plugin generating
(using GIMPLE representation) some C code (which you could later pass to
GCC and compile, on Linux, as a shared object)
Regards.
--
Basile Starynkevitch -http://starynkevitch.net/Basile/
email:<basile@starynkevitch.net> (near Paris, France)
only mines opinions - les opinions sont seulement miennes
next parent reply other threads:[~2023-10-07 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xUyN-um9ScbmLylXsJiiBi5lDN-EqVJrG7l2Twf_EURFKAXh5KnTSwEbYNjnZEtTaeET3RoMqTTeDsMkz3TnQJMSFJt93gcmVQolubmOUnM=@zhuyi.fan>
2023-10-07 14:47 ` Basile Starynkevitch [this message]
2023-10-07 15:26 ` Basile Starynkevitch
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=dd29f59b-c08a-4cfa-910b-182cdce56cc1@starynkevitch.net \
--to=basile@starynkevitch.net \
--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).