From: Mark Kettenis <kettenis@chello.nl>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Fix compiler warning in i386bsd-nat.c
Date: Mon, 15 Mar 2004 23:02:00 -0000 [thread overview]
Message-ID: <200403152302.i2FN2glv026734@elgar.kettenis.dyndns.org> (raw)
Message-ID: <20040315230200.6RFEuJM_EM-r4Hm0-hbg3Ib_L5GsrXo1ubX6-iI6BiQ@z> (raw)
Some stopgap for a compiler warning in i386bsd-nat.c. I'll probably
revisit this file a few times in the near feature. I hope to devise a
more permanent solution then.
Committed to mainline,
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* i386bsd-nat.c: Update copyright year.
(CANNOT_FETCH_REGISTER, CANNOT_STORE_REGISTER): Undefine and then
define unconditionally.
Index: i386bsd-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/i386bsd-nat.c,v
retrieving revision 1.23
diff -u -p -r1.23 i386bsd-nat.c
--- i386bsd-nat.c 28 Sep 2003 13:35:44 -0000 1.23
+++ i386bsd-nat.c 15 Mar 2004 22:55:25 -0000
@@ -1,5 +1,6 @@
/* Native-dependent code for modern i386 BSD's.
- Copyright 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
+
+ Copyright 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
This file is part of GDB.
@@ -52,14 +53,12 @@ typedef struct fpreg fpregset_t;
presence, and deal gracefully with their absence. */
/* Registers we shouldn't try to fetch. */
-#if !defined (CANNOT_FETCH_REGISTER)
+#undef CANNOT_FETCH_REGISTER
#define CANNOT_FETCH_REGISTER(regno) cannot_fetch_register (regno)
-#endif
/* Registers we shouldn't try to store. */
-#if !defined (CANNOT_STORE_REGISTER)
+#undef CANNOT_STORE_REGISTER
#define CANNOT_STORE_REGISTER(regno) cannot_fetch_register (regno)
-#endif
/* Offset to the gregset_t location where REG is stored. */
#define REG_OFFSET(reg) offsetof (gregset_t, reg)
next reply other threads:[~2004-03-15 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Mark Kettenis [this message]
2004-03-15 23:02 ` Mark Kettenis
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=200403152302.i2FN2glv026734@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
/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