This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Patch: FYI: minor comment fixes
- From: Tom Tromey <tromey at redhat dot com>
- To: Gcc Patch List <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 24 Aug 2007 14:46:32 -0600
- Subject: Patch: FYI: minor comment fixes
- Reply-to: Tom Tromey <tromey at redhat dot com>
I'm checking this in on the trunk.
This fixes a few comment problems I found: a typo in varpool.c, a
repetition in c-decl.c, and an obsolete comment also in c-decl.c.
Tom
Index: ChangeLog
from Tom Tromey <tromey@redhat.com>
* varpool.c (varpool_last_needed_node): Fix comment typo.
* c-decl.c (duplicate_decls): Fix comment typo.
(clone_underlying_type): Update comment.
Index: varpool.c
===================================================================
--- varpool.c (revision 127744)
+++ varpool.c (working copy)
@@ -57,8 +57,9 @@
The queue is maintained via mark_needed_node, linked via node->next_needed
pointer.
- LAST_NNEDED_NODE points to the end of queue, so it can be maintained in forward
- order. QTY is needed to make it friendly to PCH.
+ LAST_NEEDED_NODE points to the end of queue, so it can be
+ maintained in forward order. QTY is needed to make it friendly to
+ PCH.
During unit-at-a-time compilation we construct the queue of needed variables
twice: first time it is during cgraph construction, second time it is at the
Index: c-decl.c
===================================================================
--- c-decl.c (revision 127744)
+++ c-decl.c (working copy)
@@ -1930,7 +1930,7 @@
if (!diagnose_mismatched_decls (newdecl, olddecl, &newtype, &oldtype))
{
- /* Avoid `unused variable' and other warnings warnings for OLDDECL. */
+ /* Avoid `unused variable' and other warnings for OLDDECL. */
TREE_NO_WARNING (olddecl) = 1;
return false;
}
@@ -2028,12 +2028,8 @@
Obviously, we don't want to generate a duplicate ..._TYPE node if
the TYPE_DECL node that we are now processing really represents a
- standard built-in type.
+ standard built-in type. */
- Since all standard types are effectively declared at line zero
- in the source file, we can easily check to see if we are working
- on a standard type by checking the current value of lineno. */
-
static void
clone_underlying_type (tree x)
{