From: Sergio Durigan Junior <sergiosdj@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] Move VEC (const_char_ptr) to gdb_vecs.h
Date: Fri, 20 Apr 2012 04:26:00 -0000 [thread overview]
Message-ID: <m3hawf117b.fsf@students.ic.unicamp.br> (raw)
Hi,
This patch moves the definition of VEC (const_char_ptr) to gdb_vecs.h.
It is rather obvious, but I decided to ask either way. Ok to apply?
The reason behind this change is that the next iteration of the
SystemTap integration patch is going to need it.
Thanks,
--
Sergio
2012-20-04 Sergio Durigan Junior <sergiodj@redhat.com>
* cp-support.h: Include `gdb_vecs.h'. Delete `const_char_ptr' VEC
declaration.
* gdb_vecs.h: Declare `const_char_ptr' VEC.
diff --git a/gdb/cp-support.h b/gdb/cp-support.h
index 5988418..03ccb73 100644
--- a/gdb/cp-support.h
+++ b/gdb/cp-support.h
@@ -26,6 +26,7 @@
#include "symtab.h"
#include "vec.h"
+#include "gdb_vecs.h"
#include "gdb_obstack.h"
/* Opaque declarations. */
@@ -174,8 +175,6 @@ extern struct type *cp_lookup_rtti_type (const char *name,
extern int cp_is_anonymous (const char *namespace);
-DEF_VEC_P (const_char_ptr);
-
extern void cp_add_using_directive (const char *dest,
const char *src,
const char *alias,
diff --git a/gdb/gdb_vecs.h b/gdb/gdb_vecs.h
index b9e0b14..ce32de3 100644
--- a/gdb/gdb_vecs.h
+++ b/gdb/gdb_vecs.h
@@ -25,6 +25,8 @@
DEF_VEC_P (char_ptr);
+DEF_VEC_P (const_char_ptr);
+
/* From utils.c: */
extern void free_char_ptr_vec (VEC (char_ptr) *char_ptr_vec);
next reply other threads:[~2012-04-20 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 4:26 Sergio Durigan Junior [this message]
2012-04-20 4:58 ` Sergio Durigan Junior
2012-04-20 7:21 ` Yao Qi
2012-04-20 15:02 ` Tom Tromey
2012-04-20 18:05 ` Sergio Durigan Junior
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=m3hawf117b.fsf@students.ic.unicamp.br \
--to=sergiosdj@gmail.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