From: Andrea Corallo <andrea.corallo@arm.com>
To: jit@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>, nd@arm.com
Subject: libgccjit as beta?
Date: Thu, 14 Jan 2021 23:23:39 +0100 [thread overview]
Message-ID: <gkrk0sfkvis.fsf@arm.com> (raw)
Hi Dave and all,
libgccjit is still advertized as alpha state in the documentation
despite having being introduced few years ago.
I think we may want to evaluate to promote it as beta with the following
motivations:
- The API has been incerementally refined over the years since its
introduction and it looks reasonably complete for fruition now.
- Example as the Emacs native compiler proves it can be used to create
production software.
My main concern (the main issue we are facing) is that the alpha state
shows up as a limiting factor for certain distributions to package it
[1]. Needless to say this is also a potential limitaiton for other
software to adopt it.
WDYT?
Thanks and Regards
Andrea
[1] <https://bugs.archlinux.org/task/61820>
next reply other threads:[~2021-01-14 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 22:23 Andrea Corallo [this message]
2021-01-14 23:02 ` [committed] jit: remove "Alpha" warning from docs David Malcolm
2021-01-14 23:08 ` Andrea Corallo
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=gkrk0sfkvis.fsf@arm.com \
--to=andrea.corallo@arm.com \
--cc=dmalcolm@redhat.com \
--cc=jit@gcc.gnu.org \
--cc=nd@arm.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).