From: Christian Weisgerber <naddy@mips.inka.de>
To: Bruno Haible <bruno@clisp.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, bug-gnulib@gnu.org
Subject: Re: sigsegv.c: add OpenBSD/powerpc64 support
Date: Mon, 13 Sep 2021 21:37:25 +0200 [thread overview]
Message-ID: <YT+odeg4WLQsxfXM@lorvorc.mips.inka.de> (raw)
In-Reply-To: <4694160.tiCG3LdiiZ@omega>
Bruno Haible:
> The patch looks right; it is consistent with
> https://cvsweb.openbsd.org/src/sys/arch/powerpc64/include/signal.h?rev=1.5&content-type=text/x-cvsweb-markup .
> But has it also been tested? The test procedure is to create a testdir of
> this gnulib module:
> [...]
> Which tests pass, which tests fail?
All tests pass:
make check-TESTS
PASS: test-intprops
PASS: test-inttypes
PASS: test-limits-h
PASS: test-sigsegv-catch-segv1
PASS: test-sigsegv-catch-segv2
PASS: test-sigsegv-catch-stackoverflow1
PASS: test-sigsegv-catch-stackoverflow2
PASS: test-stdalign
PASS: test-stdbool
PASS: test-stddef
PASS: test-stdint
PASS: test-stdlib
PASS: test-sys_types
PASS: test-init.sh
PASS: test-unistd
PASS: test-verify
PASS: test-verify.sh
PASS: test-wchar
============================================================================
Testsuite summary for dummy 0
============================================================================
# TOTAL: 18
# PASS: 18
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
--
Christian "naddy" Weisgerber naddy@mips.inka.de
next prev parent reply other threads:[~2021-09-13 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 20:19 sigsegv.c: add OpenBSD/powerpc64 support Christian Weisgerber
2021-09-11 20:53 ` Paul Eggert
2021-09-11 22:42 ` Christian Weisgerber
2021-09-11 23:01 ` Bruno Haible
2021-09-13 19:37 ` Christian Weisgerber [this message]
2021-09-13 23:12 ` Bruno Haible
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=YT+odeg4WLQsxfXM@lorvorc.mips.inka.de \
--to=naddy@mips.inka.de \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).