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 18:51:00 -0000 [thread overview]
Message-ID: <200611281850.kASIoxaU008674@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20061128152857.GD17349@nevyn.them.org> from "Daniel Jacobowitz" at Nov 28, 2006 10:28:57 AM
Daniel Jacobowitz wrote:
> > For Linux, the nm-linux.h file already defines those macros, so the
> > definitions in the tm files appear to be fully redundant.
>
> The nm-linux.h define is redundant too, isn't it? And off by one?
> Compare to the top of signals.c. Or is the copy in signals.c off by
> one?
Right. The nm-linux.h define should be redundant too. However, it
is actually the correct version; the one at the top of signals.c
is off by one. (SIGRTMAX is the number of last real-time signal,
REALTIME_HI is supposed to be one beyond the number of the last
real-time signal.)
So we should fix the default definition in signals.c, and then
remove the redundant define in nm-linux.h. In fact, this would
allow to remove the #include <signal.h> from nm-linux.h as well,
but that *might* cause breakage if any of the native Linux targets
happens to rely on that implicit inclusion of <signal.h>.
That's unfortunately a bit hard to test for ...
> Patch looks OK modulo that question.
Would it be OK to commit the current patch as-is, and do the removal
from nm-linux.h as a follow-on patch?
Thanks,
Ulrich
--
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 18:51 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 [this message]
2006-11-28 18:56 ` Daniel Jacobowitz
2006-11-28 19:40 ` Ulrich Weigand
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=200611281850.kASIoxaU008674@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