From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Remove REALTIME_HI/LO macros from target headers
Date: Tue, 28 Nov 2006 19:40:00 -0000 [thread overview]
Message-ID: <200611281939.kASJdiMQ006242@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20061128185608.GA27151@nevyn.them.org> from "Daniel Jacobowitz" at Nov 28, 2006 01:56:08 PM
Daniel Jacobowitz wrote:
> I'm not too worried about it. Let's assume it won't be a problem, and
> if it is, it's easy to fix.
OK, fine with me.
> > Would it be OK to commit the current patch as-is, and do the removal
> > from nm-linux.h as a follow-on patch?
>
> Yes, that's fine; the current patch is OK.
Thanks; I've committed the patch now.
Here's the follow-on patch to remove the definition from nm-linux.h
as well; tested on s390-ibm-linux and s390x-ibm-linux. OK?
Bye,
Ulrich
ChangeLog:
* config/nm-linux.h: Do not include <signal.h>.
(REALTIME_LO, REALTIME_HI): Do not define.
* signals/signals.c (REALTIME_HI): Fix off-by-one bug.
diff -ur gdb-orig/gdb/config/nm-linux.h gdb-head/gdb/config/nm-linux.h
--- gdb-orig/gdb/config/nm-linux.h 2006-11-24 19:29:57.000000000 +0100
+++ gdb-head/gdb/config/nm-linux.h 2006-11-28 20:02:26.533200576 +0100
@@ -25,16 +25,6 @@
/* GNU/Linux is SVR4-ish but its /proc file system isn't. */
#undef USE_PROC_FS
-/* Since we're building a native debugger, we can include <signal.h>
- to find the range of real-time signals. */
-
-#include <signal.h>
-
-#ifdef __SIGRTMIN
-#define REALTIME_LO __SIGRTMIN
-#define REALTIME_HI (__SIGRTMAX + 1)
-#endif
-
extern void lin_lwp_attach_lwp (ptid_t ptid, int verbose);
#define ATTACH_LWP(ptid, verbose) lin_lwp_attach_lwp ((ptid), (verbose))
diff -ur gdb-orig/gdb/signals/signals.c gdb-head/gdb/signals/signals.c
--- gdb-orig/gdb/signals/signals.c 2005-12-23 20:05:48.000000000 +0100
+++ gdb-head/gdb/signals/signals.c 2006-11-28 20:02:43.954215168 +0100
@@ -37,10 +37,10 @@
#ifndef REALTIME_LO
# if defined(__SIGRTMIN)
# define REALTIME_LO __SIGRTMIN
-# define REALTIME_HI __SIGRTMAX
+# define REALTIME_HI (__SIGRTMAX + 1)
# elif defined(SIGRTMIN)
# define REALTIME_LO SIGRTMIN
-# define REALTIME_HI SIGRTMAX
+# define REALTIME_HI (SIGRTMAX + 1)
# endif
#endif
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2006-11-28 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 21:13 Ulrich Weigand
2006-11-28 15:29 ` Daniel Jacobowitz
2006-11-28 18:51 ` Ulrich Weigand
2006-11-28 18:56 ` Daniel Jacobowitz
2006-11-28 19:40 ` Ulrich Weigand [this message]
2006-11-28 19:41 ` Daniel Jacobowitz
2006-11-28 19:50 ` Ulrich Weigand
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=200611281939.kASJdiMQ006242@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.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