[wwwdocs] Add libgccjit to gcc-5/changes.html

This patch adds an <h2>-level section about libgccjit between the
sections on languages and targets.

It has various links to the documentation (now that that's on the
website), and to a couple of 3rd party repos (the Python and D
bindings).  It also mentions the license of the library.

OK to commit?

Dave

On Thu, 2015-02-05 at 21:47 -0500, David Malcolm wrote:
> This patch adds an <h2>-level section about libgccjit between the
> sections on languages and targets.
> 
> It has various links to the documentation (now that that's on the
> website), and to a couple of 3rd party repos (the Python and D
> bindings).  It also mentions the license of the library.
> 
> OK to commit?
> 
> Dave

Ping re: https://gcc.gnu.org/ml/gcc-patches/2015-02/msg00371.html

(although the patch is slightly mangled in that HTML rendering in the
archive, where semicolons have somehow been injected in the tags; the
markup is correct in the patch itself).

Hi David,

On Thu, 5 Feb 2015, David Malcolm wrote:
> This patch adds an <h2>-level section about libgccjit 
> between the sections on languages and targets.

this is a very nice idea.

Index: htdocs/gcc-5/changes.html
===================================================================
+<h2 id="jit">libgccjit</h2>
+<p>New in GCC 5 is the ability to build gcc as a shared library for embedding
+in other processes (such as interpreters), suitable for Just-In-Time
+compilation to machine code.</p>

"GCC" (in "build GCC as"), and the line looks a bit long?

+<p>The library can also be used for ahead-of-time compilation, enabling
+GCC to be plugged into a pre-existing frontend.

I have to admit that to me "pre-existing" always feels a bit redundant.  
Does that come before "regular existing" and "post-existing"? ;-) Tongue
in cheek, and probably because I am not a native speaker?


This is okay with this change and considering (which does not
necessarily mean honoring) the comment.

Thank you.

Gerald

David Malcolm wrote:
> On Thu, 2015-02-05 at 21:47 -0500, David Malcolm wrote:
>> This patch adds an <h2>-level section about libgccjit between the
>> sections on languages and targets.
>>
>> It has various links to the documentation (now that that's on the
>> website), and to a couple of 3rd party repos (the Python and D
>> bindings).  It also mentions the license of the library.
>>
>> OK to commit?
>
> Ping re: https://gcc.gnu.org/ml/gcc-patches/2015-02/msg00371.html
>
> (although the patch is slightly mangled in that HTML rendering in the
> archive, where semicolons have somehow been injected in the tags; the
> markup is correct in the patch itself).

While it would be nice if Gerald could find the time to review the 
patch, I recall that he once said that maintainers don't need approvals 
for release-notes changes of their part of the compiler, which also 
matches what is written at https://gcc.gnu.org/svnwrite.html#policies :

"These folks are allowed to make changes to areas they maintain and 
related documentation, web pages, and test cases without approval from 
anyone else, and approve other people's changes in those areas."

And as you are JIT maintainer ...

Cheers,

Tobias

On Sun, 1 Mar 2015, Tobias Burnus wrote:
>> Ping re: https://gcc.gnu.org/ml/gcc-patches/2015-02/msg00371.html
> While it would be nice if Gerald could find the time to review the patch, 
> I recall that he once said that maintainers don't need approvals for
> release-notes changes of their part of the compiler, which also matches 
> what is written at https://gcc.gnu.org/svnwrite.html#policies :

Yep, absolutely agreed.

That said, I actually did review and approve this specific patch, cf.
  https://gcc.gnu.org/ml/gcc-patches/2015-02/msg01672.html

And I am always happy to review (and/or provide some editing after
a commit), but outside of news items on the main page which generally 
should be reviewed by a second pair of eyes than the contributor this
is more of a service than a mandate. ;-)

Gerald

On Fri, 2015-02-27 at 01:06 +0100, Gerald Pfeifer wrote:
> Hi David,
> 
> On Thu, 5 Feb 2015, David Malcolm wrote:
> > This patch adds an <h2>-level section about libgccjit 
> > between the sections on languages and targets.
> 
> this is a very nice idea.
> 
> Index: htdocs/gcc-5/changes.html
> ===================================================================
> +<h2 id="jit">libgccjit</h2>
> +<p>New in GCC 5 is the ability to build gcc as a shared library for embedding
> +in other processes (such as interpreters), suitable for Just-In-Time
> +compilation to machine code.</p>
> 
> "GCC" (in "build GCC as"), and the line looks a bit long?

I've capitalized the "GCC".

> +<p>The library can also be used for ahead-of-time compilation, enabling
> +GCC to be plugged into a pre-existing frontend.
> 
> I have to admit that to me "pre-existing" always feels a bit redundant.  
> Does that come before "regular existing" and "post-existing"? ;-) Tongue
> in cheek, and probably because I am not a native speaker?

FWIW I am a native speaker.  I was trying to stress that this gives
people the ability to use libgccjit with code that already exists
(assuming that the licenses are compatible, which is mentioned lower
down); "pre-existing" seems to be the best way to express that, so I've
kept it.

> This is okay with this change and considering (which does not
> necessarily mean honoring) the comment.
> 
> Thank you.

Thanks; committed.

Dave