Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [RFA 1/4] Make c_type_print_varspec_suffix static
Date: Tue, 17 Apr 2018 19:51:00 -0000	[thread overview]
Message-ID: <20180417195125.14200-2-tom@tromey.com> (raw)
In-Reply-To: <20180417195125.14200-1-tom@tromey.com>

I noticed that c_type_print_varspec_suffix is only called from
c-typeprint.c, so this patch makes it "static".

ChangeLog
2018-04-17  Tom Tromey  <tom@tromey.com>

	* typeprint.h (c_type_print_varspec_suffix): Don't declare.
	* c-typeprint.c (c_type_print_varspec_suffix): Now static.
---
 gdb/ChangeLog     | 5 +++++
 gdb/c-typeprint.c | 6 +++++-
 gdb/typeprint.h   | 3 ---
 3 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/gdb/c-typeprint.c b/gdb/c-typeprint.c
index 1a8af78669..e26687ba25 100644
--- a/gdb/c-typeprint.c
+++ b/gdb/c-typeprint.c
@@ -50,6 +50,10 @@ enum access_specifier
   s_protected
 };
 
+static void c_type_print_varspec_suffix (struct type *, struct ui_file *, int,
+					 int, int,
+					 const struct type_print_options *);
+
 static void c_type_print_varspec_prefix (struct type *,
 					 struct ui_file *,
 					 int, int, int,
@@ -716,7 +720,7 @@ remove_qualifiers (char *qid)
    needed after the variable name (to describe its type).
    Args work like c_type_print_varspec_prefix.  */
 
-void
+static void
 c_type_print_varspec_suffix (struct type *type,
 			     struct ui_file *stream,
 			     int show, int passed_a_ptr,
diff --git a/gdb/typeprint.h b/gdb/typeprint.h
index 895eebd50a..74006b3058 100644
--- a/gdb/typeprint.h
+++ b/gdb/typeprint.h
@@ -120,9 +120,6 @@ private:
 
 void print_type_scalar (struct type * type, LONGEST, struct ui_file *);
 
-void c_type_print_varspec_suffix (struct type *, struct ui_file *, int,
-				  int, int, const struct type_print_options *);
-
 void c_type_print_args (struct type *, struct ui_file *, int, enum language,
 			const struct type_print_options *);
 
-- 
2.13.6


  parent reply	other threads:[~2018-04-17 19:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 19:51 [RFA 0/4] Remove TYPE_TAG_NAME Tom Tromey
2018-04-17 19:51 ` [RFA 4/4] Remove type_name_no_tag and rename type_name_no_tag_or_error Tom Tromey
2018-05-31  6:22   ` Joel Brobecker
2018-04-17 19:51 ` [RFA 2/4] Thread language through c_type_print_args Tom Tromey
2018-04-18 17:53   ` Tom Tromey
2018-05-31  1:37   ` Joel Brobecker
2018-04-17 19:51 ` Tom Tromey [this message]
2018-05-31  1:33   ` [RFA 1/4] Make c_type_print_varspec_suffix static Joel Brobecker
2018-04-17 19:51 ` [RFA 3/4] Remove TYPE_TAG_NAME Tom Tromey
2018-04-18 16:57   ` Keith Seitz
2018-04-18 17:57     ` Tom Tromey
2018-04-18 18:06       ` Keith Seitz
2018-05-31  2:35   ` Joel Brobecker
2018-04-18 16:57 ` [RFA 0/4] " Keith Seitz
2018-05-09 15:42 ` Tom Tromey
2018-05-25 17:30   ` Tom Tromey

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=20180417195125.14200-2-tom@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.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