From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>, <gdb-patches@sourceware.org>
Subject: Re: Warnings in native MinGW32 build of GDB 7.8
Date: Wed, 13 Aug 2014 04:11:00 -0000 [thread overview]
Message-ID: <53EAE47A.6030700@codesourcery.com> (raw)
In-Reply-To: <83r40plpp3.fsf@gnu.org>
On 08/09/2014 10:09 PM, Eli Zaretskii wrote:
> I fixed that as below, but I wonder why no one else saw this. is this
> because I use an ancient version of GCC?
I don't see any warning in my mingw32 build. I am using
i686-w64-mingw32-gcc 4.8.2.
>
> OK to commit the below (master and 7.8 branch), with suitable
> ChangeLog entries?
>
> --- gdb/dcache.c~0 2014-07-29 15:37:42.000000000 +0300
> +++ gdb/dcache.c 2014-08-09 16:17:31.823000000 +0300
> @@ -18,6 +18,7 @@
> along with this program. If not, see <http://www.gnu.org/licenses/>. */
>
> #include "defs.h"
> +#include "target.h" /* for 'enum target_xfer_status' */
I can see enum target_xfer_status is used in this c file. This is good
to me.
> #include "dcache.h"
> #include "gdbcmd.h"
> #include <string.h>
>
> --- gdb/defs.h~0 2014-07-29 15:37:42.000000000 +0300
> +++ gdb/defs.h 2014-08-09 15:33:59.666750000 +0300
> @@ -628,6 +628,7 @@
> #endif /* alloca not defined */
>
> /* Dynamic target-system-dependent parameters for GDB. */
> +#include "frame.h" /* for 'struct frame_id' */
It is unclear to me why do we need this include?
> #include "gdbarch.h"
>
> /* * Maximum size of a register. Something small, but large enough for
>
> --- gdb/target-dcache.c~0 2014-06-11 19:34:41.000000000 +0300
> +++ gdb/target-dcache.c 2014-08-09 16:17:42.244875000 +0300
> @@ -16,6 +16,7 @@
> along with this program. If not, see <http://www.gnu.org/licenses/>. */
>
> #include "defs.h"
> +#include "target.h" /* for 'enum target_xfer_status' */
enum target_xfer_status isn't used in target-dcache.c. Do we really
need this?
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-08-13 4:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 14:10 Eli Zaretskii
2014-08-13 4:11 ` Yao Qi [this message]
2014-08-13 15:21 ` Eli Zaretskii
2014-08-13 17:42 ` Joel Brobecker
2014-08-13 18:02 ` Eli Zaretskii
2014-08-13 18:10 ` Joel Brobecker
2014-08-13 18:26 ` Joel Brobecker
2014-08-13 18:48 ` Eli Zaretskii
2014-08-15 12:33 ` Joel Brobecker
2014-08-15 14:22 ` Eli Zaretskii
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=53EAE47A.6030700@codesourcery.com \
--to=yao@codesourcery.com \
--cc=eliz@gnu.org \
--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