bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Andrey Savchenko <bircoph@altlinux.org>
Cc: Ivan Zakharyaschev <imz@altlinux.org>, bug-gnulib@gnu.org
Subject: Re: [RFC PATCH] test-c-stack2.sh: skip if the platform sent SIGILL on an invalid address.
Date: Sat, 29 Dec 2018 15:03:07 +0100	[thread overview]
Message-ID: <13689434.cqUXT2F4i2@omega> (raw)
In-Reply-To: <20181229143111.6c78b9849a8a681a47a420a0@altlinux.org>

Andrey Savchenko wrote:
> This is not possible. Four generations of hardware are already
> manufactured and they use SIGILL for such cases. It may be fixed in
> future generations if CPU designers will agree to do so

The mapping from hardware exception code to Unix signal number is done in
software, not in hardware. For an example, look in
linux-4.20/arch/sparc/mm/fault_32.c.

Bruno



  reply	other threads:[~2018-12-29 14:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 12:50 [RFC PATCH] test-c-stack2.sh: skip if the platform sent SIGILL on an invalid address Ivan Zakharyaschev
2018-12-20  2:24 ` Bruno Haible
2018-12-28 14:23   ` Ivan Zakharyaschev
2018-12-29 11:17     ` Bruno Haible
2018-12-29 11:31       ` Andrey Savchenko
2018-12-29 14:03         ` Bruno Haible [this message]
2018-12-29 14:31         ` Dmitry V. Levin
2018-12-29 14:54       ` Bruno Haible
2018-12-29 15:03       ` Ivan Zakharyaschev
2018-12-29 16:30         ` Dmitry V. Levin
2018-12-29 20:13         ` Ivan Zakharyaschev
2018-12-30  4:49           ` Bruno Haible
2018-12-29 13:54     ` Dmitry V. Levin
2018-12-29 15:15       ` Ivan Zakharyaschev

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13689434.cqUXT2F4i2@omega \
    --to=bruno@clisp.org \
    --cc=bircoph@altlinux.org \
    --cc=bug-gnulib@gnu.org \
    --cc=imz@altlinux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).