On Fri, 28 Jan 2011 14:43:28 +0200 Laurynas Biveinis <laurynas.bivei...@gmail.com> wrote:
> I have just added a new section (approved by Gerald) to the bottom of > http://gcc.gnu.org/gcc-4.6/changes.html > > Its intention is to mention noteworthy internal changes, i.e. changes > interesting for, say, maintainers of backends/frontends outside the > tree, and of course plugin developers upgrading from 4.5 to 4.6. > I am not sure to understand what is the social rules to modify that. I suppose that any patch to that page should be approved with the same strong process as patches to trunk code? I am not sure to understand the technical ways to modify that; is CVS still mandatory? That page says. >>> The gengtype utility, which previously was internal to the GCC build >>> process, has been >>> enchanced to provide GC root information for plugins as necessary. Perhaps we should mention the gtype.state file also. Unfortunately, neither gengtype nor gtype.state are installed (unless someone pushed a patch for that which I did not pay attention to; I certainly didn't). So perhaps a possible phrasing might eventually become The gengtype utility, which previously was internal to the GCC build process, has been enchanced to provide GC root information for plugins as necessary. The entire internal state of gengtype (describing the large set of GTY-ed types) is now persistent (in file gtype.state). Therefore, plugins can use GTY annotations without needing the availability of the GCC compiler source and build trees Comments are welcome. Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mine, sont seulement les miennes} ***
