public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-alpha@sourceware.org, Helge Deller <deller@gmx.de>
Subject: Re: [committed] hppa: undef __ASSUME_SET_ROBUST_LIST
Date: Wed, 21 Sep 2022 10:11:41 -0400	[thread overview]
Message-ID: <aca64bce-0479-edd6-03a2-e164a0e15de6@bell.net> (raw)
In-Reply-To: <mvmleqcq0un.fsf@suse.de>

On 2022-09-21 10:05 a.m., Andreas Schwab wrote:
> On Sep 21 2022, John David Anglin wrote:
>
>>     tst-cancel24 triggered my interest, so I checked what's doing:
>>     #>  QEMU_LOG=strace ./glibc-2.34/build-tree/hppa-libc/nptl/tst-cancel24
>>     ...
>>     2080424 set_robust_list(-105721680,12,0,-105720464,-100671382,1) = -1 errno=251 (Function not implemented)
> This test doesn't fail for me for riscv64 with qemu.  Others on your
> list also do not fail here.
It depends on the kernel version reported by qemu on riscv:

/* No support for PI mutexes or robust futexes before 4.20.  */
#if __LINUX_KERNEL_VERSION < 0x041400
# undef __ASSUME_SET_ROBUST_LIST
#endif

-- 
John David Anglin  dave.anglin@bell.net


  reply	other threads:[~2022-09-21 14:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 20:20 John David Anglin
2022-09-21  7:41 ` Andreas Schwab
2022-09-21 13:52   ` John David Anglin
2022-09-21 14:05     ` Andreas Schwab
2022-09-21 14:11       ` John David Anglin [this message]
2022-09-21 14:23         ` Andreas Schwab
2022-09-21 12:16 ` Adhemerval Zanella Netto
2022-09-21 12:49   ` Florian Weimer
2022-09-21 12:59     ` Andreas Schwab
2022-09-21 13:56     ` Adhemerval Zanella Netto
2022-09-22 12:18       ` Florian Weimer

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=aca64bce-0479-edd6-03a2-e164a0e15de6@bell.net \
    --to=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@suse.de \
    /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).