From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, borntraeger@de.ibm.com
Subject: [Qemu-devel] [PATCH] tcg/s390: Remove sigill_handler
Date: Wed, 29 Jan 2014 13:08:30 -0800 [thread overview]
Message-ID: <1391029710-11780-1-git-send-email-rth@twiddle.net> (raw)
Commit c9baa30f42a87f61627391698f63fa4d1566d9d8 failed to
delete all of the relevant code, leading to Werrors about
unused symbols.
Signed-off-by: Richard Henderson <rth@twiddle.net>
---
tcg/s390/tcg-target.c | 19 -------------------
1 file changed, 19 deletions(-)
diff --git a/tcg/s390/tcg-target.c b/tcg/s390/tcg-target.c
index 248726e..907d9d1 100644
--- a/tcg/s390/tcg-target.c
+++ b/tcg/s390/tcg-target.c
@@ -2214,25 +2214,6 @@ static const TCGTargetOpDef s390_op_defs[] = {
{ -1 },
};
-/* ??? Linux kernels provide an AUXV entry AT_HWCAP that provides most of
- this information. However, getting at that entry is not easy this far
- away from main. Our options are: start searching from environ, but
- that fails as soon as someone does a setenv in between. Read the data
- from /proc/self/auxv. Or do the probing ourselves. The only thing
- extra that AT_HWCAP gives us is HWCAP_S390_HIGH_GPRS, which indicates
- that the kernel saves all 64-bits of the registers around traps while
- in 31-bit mode. But this is true of all "recent" kernels (ought to dig
- back and see from when this might not be true). */
-
-#include <signal.h>
-
-static volatile sig_atomic_t got_sigill;
-
-static void sigill_handler(int sig)
-{
- got_sigill = 1;
-}
-
static void query_facilities(void)
{
unsigned long hwcap = qemu_getauxval(AT_HWCAP);
--
1.8.5.3
next reply other threads:[~2014-01-29 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 21:08 Richard Henderson [this message]
2014-02-01 9:45 ` [Qemu-devel] [Qemu-trivial] [PATCH] tcg/s390: Remove sigill_handler Michael Tokarev
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=1391029710-11780-1-git-send-email-rth@twiddle.net \
--to=rth@twiddle.net \
--cc=borntraeger@de.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 NNTP newsgroup(s).