From: David Malcolm <dmalcolm@redhat.com>
To: Andrea Corallo <andrea.corallo@arm.com>,
jit@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: nd@arm.com, David Malcolm <dmalcolm@redhat.com>
Subject: [committed] jit: remove "Alpha" warning from docs
Date: Thu, 14 Jan 2021 18:02:52 -0500 [thread overview]
Message-ID: <20210114230252.3860992-1-dmalcolm@redhat.com> (raw)
In-Reply-To: <gkrk0sfkvis.fsf@arm.com>
On Thu, 2021-01-14 at 23:23 +0100, Andrea Corallo wrote:
> 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>
Thanks for pointing this out. I've pushed the following patch to master
for gcc 11, as b95d97f1a5f54f55c15bca65ec79b626b53cd40c:
I removed the "Alpha" warning from the JIT wiki page on
2020-05-18:
https://gcc.gnu.org/wiki/JIT?action=diff&rev1=47&rev2=48
but forgot to remove it from the documentation, which this
patch does.
gcc/jit/ChangeLog:
* docs/cp/index.rst: Remove "Alpha" warning.
* docs/index.rst: Likewise.
---
gcc/jit/docs/cp/index.rst | 4 ----
gcc/jit/docs/index.rst | 4 ----
2 files changed, 8 deletions(-)
diff --git a/gcc/jit/docs/cp/index.rst b/gcc/jit/docs/cp/index.rst
index 254ad59819e..3bffc98a3de 100644
--- a/gcc/jit/docs/cp/index.rst
+++ b/gcc/jit/docs/cp/index.rst
@@ -28,10 +28,6 @@ This is a collection of "thin" wrapper classes around the C API.
Everything is an inline function, implemented in terms of the C API,
so there is nothing extra to link against.
-Note that libgccjit is currently of "Alpha" quality;
-the APIs are not yet set in stone, and they shouldn't be used in
-production yet.
-
Contents:
.. toctree::
diff --git a/gcc/jit/docs/index.rst b/gcc/jit/docs/index.rst
index 4db1ddd8307..fe3d741d345 100644
--- a/gcc/jit/docs/index.rst
+++ b/gcc/jit/docs/index.rst
@@ -21,10 +21,6 @@ libgccjit
This document describes `libgccjit <http://gcc.gnu.org/wiki/JIT>`_, an API
for embedding GCC inside programs and libraries.
-Note that libgccjit is currently of "Alpha" quality;
-the APIs are not yet set in stone, and they shouldn't be used in
-production yet.
-
There are actually two APIs for the library:
* a pure C API: ``libgccjit.h``
--
2.26.2
next prev parent reply other threads:[~2021-01-14 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 22:23 libgccjit as beta? Andrea Corallo
2021-01-14 23:02 ` David Malcolm [this message]
2021-01-14 23:08 ` [committed] jit: remove "Alpha" warning from docs 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=20210114230252.3860992-1-dmalcolm@redhat.com \
--to=dmalcolm@redhat.com \
--cc=andrea.corallo@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--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).