From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [committed] hppa: undef __ASSUME_SET_ROBUST_LIST
Date: Wed, 21 Sep 2022 09:16:44 -0300 [thread overview]
Message-ID: <d3a7fff0-7d37-aedb-7d2f-e88cdef89387@linaro.org> (raw)
In-Reply-To: <YyoghuufsX7+v4e/@mx3210.localdomain>
On 20/09/22 17:20, John David Anglin wrote:
> QEMU does not support support set_robust_list. Thus, we need
> to enable detection of set_robust_list system call.
>
> Signed-off-by: John David Anglin <dave.anglin@bell.net>
> ---
> diff --git a/sysdeps/unix/sysv/linux/hppa/kernel-features.h b/sysdeps/unix/sysv/linux/hppa/kernel-features.h
> index 0cd21ef0fa..079612e4aa 100644
> --- a/sysdeps/unix/sysv/linux/hppa/kernel-features.h
> +++ b/sysdeps/unix/sysv/linux/hppa/kernel-features.h
> @@ -30,3 +30,6 @@
>
> #undef __ASSUME_CLONE_DEFAULT
> #define __ASSUME_CLONE_BACKWARDS 1
> +
> +/* QEMU does not support set_robust_list. */
> +#undef __ASSUME_SET_ROBUST_LIST
>
Does it happen only for hppa? If is a generic missing feature maybe we should
undef __ASSUME_SET_ROBUST_LIST for all architectures.
next prev parent reply other threads:[~2022-09-21 12:16 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
2022-09-21 14:23 ` Andreas Schwab
2022-09-21 12:16 ` Adhemerval Zanella Netto [this message]
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=d3a7fff0-7d37-aedb-7d2f-e88cdef89387@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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).