public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
* libgccjit as beta?
@ 2021-01-14 22:23 Andrea Corallo
  2021-01-14 23:02 ` [committed] jit: remove "Alpha" warning from docs David Malcolm
  0 siblings, 1 reply; 3+ messages in thread
From: Andrea Corallo @ 2021-01-14 22:23 UTC (permalink / raw)
  To: jit; +Cc: David Malcolm, nd

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>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [committed] jit: remove "Alpha" warning from docs
  2021-01-14 22:23 libgccjit as beta? Andrea Corallo
@ 2021-01-14 23:02 ` David Malcolm
  2021-01-14 23:08   ` Andrea Corallo
  0 siblings, 1 reply; 3+ messages in thread
From: David Malcolm @ 2021-01-14 23:02 UTC (permalink / raw)
  To: Andrea Corallo, jit, gcc-patches; +Cc: nd, David Malcolm

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [committed] jit: remove "Alpha" warning from docs
  2021-01-14 23:02 ` [committed] jit: remove "Alpha" warning from docs David Malcolm
@ 2021-01-14 23:08   ` Andrea Corallo
  0 siblings, 0 replies; 3+ messages in thread
From: Andrea Corallo @ 2021-01-14 23:08 UTC (permalink / raw)
  To: David Malcolm; +Cc: jit, gcc-patches, nd

David Malcolm <dmalcolm@redhat.com> writes:

> 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:

Super! Thanks!

  Andrea

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-01-14 23:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-14 22:23 libgccjit as beta? Andrea Corallo
2021-01-14 23:02 ` [committed] jit: remove "Alpha" warning from docs David Malcolm
2021-01-14 23:08   ` Andrea Corallo

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).