From: Doug Evans <xdje42@gmail.com>
To: Gary Benson <gbenson@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: Remove conditionals for ANSI-standard signals
Date: Thu, 05 Jun 2014 16:10:00 -0000 [thread overview]
Message-ID: <CAP9bCMRO4A5x3wkCc-XQdiWM5RPX_4QZrD_6U657deSqPCHwhQ@mail.gmail.com> (raw)
In-Reply-To: <20140605145053.GA15133@blade.nx>
On Thu, Jun 5, 2014 at 7:50 AM, Gary Benson <gbenson@redhat.com> wrote:
> Hi all,
>
> This patch removes all preprocessor conditionals for ANSI-standard
> signals (SIGINT, SIGILL, SIGABRT, SIGFPE, SIGSEGV and SIGTERM) which
> are guaranteed to always be defined.
>
> Built and regtested on RHEL6.5 x86_64.
>
> Ok to commit?
>
> Cheers,
> Gary
>
> --
> gdb/
> 2014-06-05 Gary Benson <gbenson@redhat.com>
>
> * common/signals.c: Remove preprocessor conditionals for
> always-defined signals SIGINT, SIGILL, SIGABRT, SIGFPE,
> SIGSEGV and SIGTERM.
> * proc-events.c: Likewise.
Ok, with one request.
IWBN to have one more patch after this one, as its preferable to move
code around as a separate patch.
I can't see any sorting order to the places that have all the #ifdefs
(common/signals.c in particular), and I wonder if it would be useful
to put the non-#ifdef'd signals first with a comment explaining why
they don't have #ifdefs.
One could also sort them alphabetically of course too, of course,
within each group (non-#ifdef, #ifdef), but I don't have a strong
opinion on that.
next prev parent reply other threads:[~2014-06-05 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 14:51 Gary Benson
2014-06-05 15:28 ` Eli Zaretskii
2014-06-05 15:37 ` Gary Benson
2014-06-05 16:10 ` Doug Evans [this message]
2014-06-05 17:29 ` Eli Zaretskii
2014-06-06 9:27 ` [COMMITTED PATCH] " Gary Benson
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=CAP9bCMRO4A5x3wkCc-XQdiWM5RPX_4QZrD_6U657deSqPCHwhQ@mail.gmail.com \
--to=xdje42@gmail.com \
--cc=eliz@gnu.org \
--cc=gbenson@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