From: Florian Weimer <fweimer@redhat.com>
To: Evan Green <evan@rivosinc.com>
Cc: libc-alpha@sourceware.org, vineetg@rivosinc.com,
slewis@rivosinc.com, palmer@rivosinc.com
Subject: Re: [PATCH v12 5/7] riscv: Enable multi-arg ifunc resolvers
Date: Fri, 16 Feb 2024 08:45:01 +0100 [thread overview]
Message-ID: <8734ts7szm.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20240214143159.2951158-6-evan@rivosinc.com> (Evan Green's message of "Wed, 14 Feb 2024 06:31:56 -0800")
* Evan Green:
> diff --git a/include/libc-symbols.h b/include/libc-symbols.h
> index e21bb599b3..4367aa6740 100644
> --- a/include/libc-symbols.h
> +++ b/include/libc-symbols.h
> @@ -667,9 +667,9 @@ for linking")
> #endif
>
> /* Helper / base macros for indirect function symbols. */
> -#define __ifunc_resolver(type_name, name, expr, arg, init, classifier) \
> +#define __ifunc_resolver(type_name, name, expr, init, classifier, ...) \
> classifier inhibit_stack_protector \
> - __typeof (type_name) *name##_ifunc (arg) \
> + __typeof (type_name) *name##_ifunc (__VA_ARGS__) \
> { \
> init (); \
> __typeof (type_name) *res = expr; \
> @@ -677,13 +677,13 @@ for linking")
> }
>
> #ifdef HAVE_GCC_IFUNC
> -# define __ifunc(type_name, name, expr, arg, init) \
> +# define __ifunc_args(type_name, name, expr, init, ...) \
> extern __typeof (type_name) name __attribute__ \
> ((ifunc (#name "_ifunc"))); \
> - __ifunc_resolver (type_name, name, expr, arg, init, static)
> + __ifunc_resolver (type_name, name, expr, init, static, __VA_ARGS__)
>
> -# define __ifunc_hidden(type_name, name, expr, arg, init) \
> - __ifunc (type_name, name, expr, arg, init)
> +# define __ifunc_args_hidden(type_name, name, expr, init, ...) \
> + __ifunc_args (type_name, name, expr, init, __VA_ARGS__)
> #else
> /* Gcc does not support __attribute__ ((ifunc (...))). Use the old behaviour
> as fallback. But keep in mind that the debug information for the ifunc
> @@ -694,18 +694,24 @@ for linking")
> different signatures. (Gcc support is disabled at least on a ppc64le
> Ubuntu 14.04 system.) */
>
> -# define __ifunc(type_name, name, expr, arg, init) \
> +# define __ifunc_args(type_name, name, expr, init, ...) \
> extern __typeof (type_name) name; \
> - __typeof (type_name) *name##_ifunc (arg) __asm__ (#name); \
> - __ifunc_resolver (type_name, name, expr, arg, init,) \
> + __typeof (type_name) *name##_ifunc (__VA_ARGS__) __asm__ (#name); \
> + __ifunc_resolver (type_name, name, expr, init, , __VA_ARGS__) \
> __asm__ (".type " #name ", %gnu_indirect_function");
>
> -# define __ifunc_hidden(type_name, name, expr, arg, init) \
> +# define __ifunc_args_hidden(type_name, name, expr, init, ...) \
> extern __typeof (type_name) __libc_##name; \
> - __ifunc (type_name, __libc_##name, expr, arg, init) \
> + __ifunc (type_name, __libc_##name, expr, __VA_ARGS__, init) \
> strong_alias (__libc_##name, name);
> #endif /* !HAVE_GCC_IFUNC */
>
> +#define __ifunc(type_name, name, expr, arg, init) \
> + __ifunc_args (type_name, name, expr, init, arg)
> +
> +#define __ifunc_hidden(type_name, name, expr, arg, init) \
> + __ifunc_args_hidden (type_name, name, expr, init, arg)
> +
> /* The following macros are used for indirect function symbols in libc.so.
> First of all, you need to have the function prototyped somewhere,
> say in foo.h:
The generic parts look good to me.
Reviewed-by: Florian Weimer <fweimer@redhat.com>
Thanks,
Florian
next prev parent reply other threads:[~2024-02-16 7:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 14:31 [PATCH v12 0/7] RISC-V: ifunced memcpy using new kernel hwprobe interface Evan Green
2024-02-14 14:31 ` [PATCH v12 1/7] riscv: Add Linux hwprobe syscall support Evan Green
2024-02-14 14:31 ` [PATCH v12 2/7] linux: Introduce INTERNAL_VSYSCALL Evan Green
2024-02-16 7:44 ` Florian Weimer
2024-02-23 23:12 ` Evan Green
2024-02-23 23:29 ` Gabriel Ravier
2024-02-24 2:06 ` Richard Henderson
2024-02-24 11:40 ` Florian Weimer
2024-02-26 16:47 ` Evan Green
2024-02-26 17:07 ` Florian Weimer
2024-02-26 17:57 ` Evan Green
2024-02-14 14:31 ` [PATCH v12 3/7] riscv: Add hwprobe vdso call support Evan Green
2024-02-14 14:31 ` [PATCH v12 4/7] riscv: Add __riscv_hwprobe pointer to ifunc calls Evan Green
2024-02-14 14:31 ` [PATCH v12 5/7] riscv: Enable multi-arg ifunc resolvers Evan Green
2024-02-16 7:45 ` Florian Weimer [this message]
2024-02-14 14:31 ` [PATCH v12 6/7] riscv: Add ifunc helper method to hwprobe.h Evan Green
2024-02-14 14:31 ` [PATCH v12 7/7] riscv: Add and use alignment-ignorant memcpy Evan Green
2024-02-14 15:16 ` [PATCH v12 0/7] RISC-V: ifunced memcpy using new kernel hwprobe interface Adhemerval Zanella Netto
2024-02-14 15:24 ` Andreas Schwab
2024-02-22 18:44 ` Palmer Dabbelt
2024-02-15 15:48 ` Evan Green
2024-02-15 15:57 ` enh
2024-02-15 16:50 ` Palmer Dabbelt
2024-02-15 17:00 ` enh
2024-02-15 17:22 ` Palmer Dabbelt
2024-02-15 18:45 ` enh
2024-02-15 18:56 ` Palmer Dabbelt
2024-02-15 17:42 ` Jessica Clarke
2024-02-15 18:52 ` enh
2024-02-15 19:09 ` Jessica Clarke
2024-02-22 19:41 ` Palmer Dabbelt
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=8734ts7szm.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=evan@rivosinc.com \
--cc=libc-alpha@sourceware.org \
--cc=palmer@rivosinc.com \
--cc=slewis@rivosinc.com \
--cc=vineetg@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 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).