From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: [PATCH] libc-test: PI mutex tests
Date: Tue, 9 Jul 2019 23:13:47 +0200 [thread overview]
Message-ID: <20190709211346.GH21055@port70.net> (raw)
In-Reply-To: <20190709183313.GP1506@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2019-07-09 14:33:13 -0400]:
> >From ed2b7eca0016b5a35b5281e950e82fa2bb511099 Mon Sep 17 00:00:00 2001
> From: Rich Felker <dalias@aerifal.cx>
> Date: Tue, 9 Jul 2019 14:29:20 -0400
> Subject: [PATCH] add PI mutex tests
>
> for robust mutex tests, the code was already setup to be run more than
> once with different attributes (pshared); I've added PI the same way.
>
> for the main mutex tests, it would take a major refactoring to test
> and report errors well for both the normal and PI cases, so I just
> duplicated the source file with PI hard-coded on. this could be
> improved later if desired.
applied.
prev parent reply other threads:[~2019-07-09 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 18:33 Rich Felker
2019-07-09 21:13 ` Szabolcs Nagy [this message]
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=20190709211346.GH21055@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).