From: "Zack Weinberg" <zack@owlfolio.org>
To: "Andreas Schwab" <schwab@linux-m68k.org>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Maybe we should get rid of ifuncs
Date: Wed, 24 Apr 2024 09:54:11 -0400 [thread overview]
Message-ID: <D0SEJHNAO87M.247R5N4JRMHVV@owlfolio.org> (raw)
In-Reply-To: <874jbrswxg.fsf@igel.home>
On Tue Apr 23, 2024 at 3:26 PM EDT, Andreas Schwab wrote:
> libgcc on powerpc uses ifuncs for selection of IEEE 128-bit float
> software vs hardware implementation (they are linked into every binary
> using long double arithmetic).
That's still selecting machine code based on characteristics of the
CPU, isn't it?
zw
next prev parent reply other threads:[~2024-04-24 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 18:14 Zack Weinberg
2024-04-23 18:39 ` enh
2024-04-23 19:46 ` Palmer Dabbelt
2024-04-24 13:56 ` Zack Weinberg
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D0SEJHNAO87M.247R5N4JRMHVV@owlfolio.org \
--to=zack@owlfolio.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).