From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>
Subject: [PATCH v2 3/6] use gdb_string.h in m32c-tdep.c
Date: Tue, 05 Nov 2013 19:09:00 -0000 [thread overview]
Message-ID: <1383675811-3274-4-git-send-email-tromey@redhat.com> (raw)
In-Reply-To: <1383675811-3274-1-git-send-email-tromey@redhat.com>
m32c-tdep.c is the last user of HAVE_STRING_H in gdb proper. It
really ought to be using gdb_string.h instead, as the rest of gdb
does.
2013-11-05 Tom Tromey <tromey@redhat.com>
* m32c-tdep.c: Use gdb_string.h.
---
gdb/ChangeLog | 4 ++++
gdb/m32c-tdep.c | 5 +----
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/gdb/m32c-tdep.c b/gdb/m32c-tdep.c
index a147c94..1b0eba5 100644
--- a/gdb/m32c-tdep.c
+++ b/gdb/m32c-tdep.c
@@ -21,10 +21,7 @@
#include <stdarg.h>
-#if defined (HAVE_STRING_H)
-#include <string.h>
-#endif
-
+#include "gdb_string.h"
#include "gdb_assert.h"
#include "elf-bfd.h"
#include "elf/m32c.h"
--
1.8.1.4
next prev parent reply other threads:[~2013-11-05 18:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 18:23 [PATCH v2 0/6] introduce common.m4 Tom Tromey
2013-11-05 18:23 ` [PATCH v2 2/6] remove link.h checks Tom Tromey
2013-11-05 19:10 ` Pedro Alves
2013-11-05 18:24 ` [PATCH v2 1/6] introduce common.m4 Tom Tromey
2013-11-05 19:09 ` Pedro Alves
2013-11-05 20:03 ` Tom Tromey
2013-11-08 12:46 ` Pedro Alves
2013-11-08 19:32 ` Tom Tromey
2013-11-08 20:10 ` Tom Tromey
2013-11-05 18:25 ` [PATCH v2 4/6] gdb configure updates Tom Tromey
2013-11-05 19:10 ` Pedro Alves
2013-11-05 19:09 ` Tom Tromey [this message]
2013-11-05 19:49 ` [PATCH v2 3/6] use gdb_string.h in m32c-tdep.c Pedro Alves
2013-11-05 19:10 ` [PATCH v2 0/6] introduce common.m4 Pedro Alves
2013-11-05 20:04 ` [PATCH v2 5/6] fix a comment in configure.ac Tom Tromey
2013-11-05 21:10 ` [PATCH v2 6/6] remove unused gdbserver configury 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=1383675811-3274-4-git-send-email-tromey@redhat.com \
--to=tromey@redhat.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