All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	 Alistair Francis <Alistair.Francis@wdc.com>,
	 linux-riscv@lists.infradead.org
Subject: Re: [PATCH] riscv: uapi: Lie about having futex()
Date: Thu, 19 Jan 2023 21:16:37 +0100	[thread overview]
Message-ID: <87pmbai8ka.fsf@igel.home> (raw)
In-Reply-To: <20230119193924.21186-1-palmer@rivosinc.com> (Palmer Dabbelt's message of "Thu, 19 Jan 2023 11:39:24 -0800")

On Jan 19 2023, Palmer Dabbelt wrote:

> diff --git a/arch/riscv/include/asm/unistd.h b/arch/riscv/include/asm/unistd.h
> index 221630bdbd07..26116686690a 100644
> --- a/arch/riscv/include/asm/unistd.h
> +++ b/arch/riscv/include/asm/unistd.h
> @@ -24,3 +24,11 @@
>  #include <uapi/asm/unistd.h>
>  
>  #define NR_syscalls (__NR_syscalls)
> +
> +/*
> + * Userspace (at least libstdc++) has come to expect SYS_futex, but we only
> + * have SYS_futex_time64 on rv32.  So just lie.
> + */
> +#ifndef __LP64__
> +#define __NR_futex __NR_futex_time64
> +#endif

This is not a uapi file, so why does this have any influence on
libstdc++?

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-01-19 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 19:39 [PATCH] riscv: uapi: Lie about having futex() Palmer Dabbelt
2023-01-19 20:16 ` Andreas Schwab [this message]
2023-01-20  8:44 ` Arnd Bergmann

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=87pmbai8ka.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=Alistair.Francis@wdc.com \
    --cc=arnd@arndb.de \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.