Message ID | 4D36AF55.2070300@gmail.com |
---|---|
State | New |
Headers | show |
On Wed, 19 Jan 2011, Laurynas Biveinis wrote: > There are GCC frontends and backends that live outside the tree and only > track major GCC releases instead of daily development in svn. Now also > with plugins, the amount of software that somehow uses GCC at the source > level is only going to increase. > > Why not try to make life easier for their maintainers and document some > of the internal GCC changes between the versions? I like this very much. Index: changes.html =================================================================== +<h2>GCC developer changes</h2> How about making this "Changing for GCC Developers" or something like this which seems more clear? + The <code>gengtype</code> utility, which previously was internal to + GCC build process, has been enchanced to provide GC root "the GCC build process" Thanks, Gerald
Index: changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.6/changes.html,v retrieving revision 1.90 diff -u -r1.90 changes.html --- changes.html 17 Jan 2011 01:55:22 -0000 1.90 +++ changes.html 19 Jan 2011 09:25:35 -0000 @@ -717,5 +717,23 @@ </li> </ul> +<h2>GCC developer changes</h2> + +<p>Note: these changes concern developers that develop GCC itself or + software that integrates with GCC, such as plugins, and not the + general GCC users.</p> + +<ul> + <li> + The <code>gengtype</code> utility, which previously was internal to + GCC build process, has been enchanced to provide GC root + information for plugins as necessary. + </li> + <li> + The old GC allocation interface of <code>ggc_alloc</code> and + friends was replaced with a type-safe alternative. + </li> +</ul> + </body> </html>