From patchwork Wed Jan 19 09:31:01 2011
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Patchwork-Submitter: Laurynas Biveinis <laurynas.biveinis@gmail.com>
X-Patchwork-Id: 79438
Return-Path: 
 <gcc-patches-return-283250-incoming=patchwork.ozlabs.org@gcc.gnu.org>
X-Original-To: incoming@patchwork.ozlabs.org
Delivered-To: patchwork-incoming@bilbo.ozlabs.org
Received: from sourceware.org (server1.sourceware.org [209.132.180.131])
	by ozlabs.org (Postfix) with SMTP id D5B7DB70DE
	for <incoming@patchwork.ozlabs.org>;
	Wed, 19 Jan 2011 20:31:18 +1100 (EST)
Received: (qmail 7776 invoked by alias); 19 Jan 2011 09:31:16 -0000
Received: (qmail 7766 invoked by uid 22791); 19 Jan 2011 09:31:15 -0000
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0	tests=AWL, BAYES_00,
	DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
	RCVD_IN_DNSWL_LOW, T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Received: from mail-ey0-f175.google.com (HELO mail-ey0-f175.google.com)
	(209.85.215.175) by sourceware.org (qpsmtpd/0.43rc1) with
	ESMTP; Wed, 19 Jan 2011 09:31:09 +0000
Received: by eya28 with SMTP id 28so283685eya.20 for
	<gcc-patches@gcc.gnu.org>; Wed, 19 Jan 2011 01:31:06 -0800 (PST)
Received: by 10.14.133.16 with SMTP id p16mr500362eei.31.1295429466700;
	Wed, 19 Jan 2011 01:31:06 -0800 (PST)
Received: from [192.168.0.50] ([79.133.236.212]) by mx.google.com with
	ESMTPS id u1sm5378109eeh.16.2011.01.19.01.31.04
	(version=SSLv3 cipher=RC4-MD5);
	Wed, 19 Jan 2011 01:31:05 -0800 (PST)
Message-ID: <4D36AF55.2070300@gmail.com>
Date: Wed, 19 Jan 2011 11:31:01 +0200
From: Laurynas Biveinis <laurynas.biveinis@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
	rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: gcc-patches@gcc.gnu.org
Subject: [RFC][wwwdocs] Internal GCC changes in 4.6
X-IsSubscribed: yes
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Unsubscribe: 
 <mailto:gcc-patches-unsubscribe-incoming=patchwork.ozlabs.org@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Delivered-To: mailing list gcc-patches@gcc.gnu.org

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 propose adding a new section at the end of
changes.html.  If the idea is acceptable in principle, then any suggestions/fixes to
language are most welcome.

Of course, then this new section needs attention from various maintainers to fill it with
content.

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>