From: "Zack Weinberg" <zack@owlfolio.org>
To: "enh" <enh@google.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Maybe we should get rid of ifuncs
Date: Wed, 24 Apr 2024 09:56:32 -0400 [thread overview]
Message-ID: <D0SELA748G3A.29OHZXTU7HD0I@owlfolio.org> (raw)
In-Reply-To: <CAJgzZormDUXPKzNTAT6tRxFYTMjH4KEUG6YmyFEotdb7s6MApw@mail.gmail.com>
On Tue Apr 23, 2024 at 2:39 PM EDT, enh wrote:
> one thing i think is interesting (having been looking at ifuncs while
> adding riscv64 support to Android) is that afaict bionic [Android's
> libc] is basically the only current user. every library i'm aware of
> (and certainly every library that's part of the OS) does _not_ use
> ifuncs, if only because iOS/macOS has no equivalent (and Windows
> too?), and if you've got to have the manual function pointer
> manipulation implementation for them...
I assume you meant "every library that's *not* part of the OS"?
> that said, for llvm at least there's work on function multi-versioning
> where the compiler basically writes the ifunc resolver. but (a) that's
> not quite finished yet (?) and (b) i haven't seen anyone _use_ it yet
> and (c) is at least by definition of being machine-generated pretty
> regular.
Do you know where to find the llvm work in progress?
zw
next prev parent reply other threads:[~2024-04-24 13:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 18:14 Maybe we should get rid of ifuncs Zack Weinberg
2024-04-23 18:39 ` enh
2024-04-23 19:46 ` Palmer Dabbelt
2024-04-24 13:56 ` Zack Weinberg [this message]
2024-04-24 14:25 ` enh
2024-04-23 18:52 ` Sam James
2024-04-23 18:54 ` Florian Weimer
2024-04-24 13:53 ` Zack Weinberg
2024-04-23 19:26 ` Andreas Schwab
2024-04-24 13:54 ` Zack Weinberg
2024-04-24 1:41 ` Richard Henderson
2024-04-24 14:43 ` Zack Weinberg
2024-04-24 15:09 ` enh
2024-04-28 0:24 ` Peter Bergner
2024-05-02 2:59 ` Michael Meissner
2024-04-30 8:42 ` Simon Josefsson
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D0SELA748G3A.29OHZXTU7HD0I@owlfolio.org \
--to=zack@owlfolio.org \
--cc=enh@google.com \
--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).