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
