From: Gary Funck <gary@intrepid.com>
To: Gcc Patches <gcc-patches@gcc.gnu.org>
Subject: [patch] c-decl.c(grokdeclarator) trivial formating fixes
Date: Fri, 01 Apr 2011 05:37:00 -0000 [thread overview]
Message-ID: <20110401053653.GD7573@intrepid.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
See attached: two places in grokdeclarartor, where extra spaces appear.
I can make this patch, or perhaps someone else can just fold it into
something they're doing? (Although I had separately made these changes
in the GUPC branch, I haven't tested them. Hopefully, they're safe
by inspection.)
- Gary
[-- Attachment #2: c-decl.c-fix-formatting.diffs.txt --]
[-- Type: text/plain, Size: 1128 bytes --]
Index: ChangeLog
===================================================================
--- ChangeLog (revision 171815)
+++ ChangeLog (working copy)
@@ -1,3 +1,7 @@
+2011-04-01 Gary Funck <gary@intrepid.com>
+
+ * c-decl.c (grokdeclarator): Fix formatting.
+
2011-03-31 Joseph Myers <joseph@codesourcery.com>
* opts.h (cl_option): Add comments to fields. Add bit-fields for
Index: c-decl.c
===================================================================
--- c-decl.c (revision 171815)
+++ c-decl.c (working copy)
@@ -5450,7 +5450,7 @@ grokdeclarator (const struct c_declarato
}
}
- /* Complain about arrays of incomplete types. */
+ /* Complain about arrays of incomplete types. */
if (!COMPLETE_TYPE_P (type))
{
error_at (loc, "array type has incomplete element type");
@@ -5936,7 +5936,7 @@ grokdeclarator (const struct c_declarato
if (storage_class == csc_register || threadp)
{
error_at (loc, "invalid storage class for function %qE", name);
- }
+ }
else if (current_scope != file_scope)
{
/* Function declaration not at file scope. Storage
next reply other threads:[~2011-04-01 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 5:37 Gary Funck [this message]
2011-04-01 11:52 ` Joseph S. Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110401053653.GD7573@intrepid.com \
--to=gary@intrepid.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).