From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Xi Ruoyao <xry111@xry111.site>,
Xi Ruoyao via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] libatomic: x86_64: Always try ifunc
Date: Sat, 03 Jun 2023 16:04:38 +0200 [thread overview]
Message-ID: <241EB9A4-2165-4BA0-9A40-4B266C7333B6@gmail.com> (raw)
In-Reply-To: <ddd5ed045307ab536e5110194371521e71876e2e.camel@xry111.site>
On 3 June 2023 15:46:02 CEST, Xi Ruoyao <xry111@xry111.site> wrote:
>Unfortunately __builtin_cpu_is performs CPU detection on runtime, not
>compile time.
Right, you were talking about configure, sorry.
next prev parent reply other threads:[~2023-06-03 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 11:25 Xi Ruoyao
2023-06-03 12:53 ` Bernhard Reutner-Fischer
2023-06-03 13:46 ` Xi Ruoyao
2023-06-03 14:04 ` Bernhard Reutner-Fischer [this message]
2023-06-09 12:37 ` Ping: " Xi Ruoyao
2023-06-09 12:49 ` Jakub Jelinek
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=241EB9A4-2165-4BA0-9A40-4B266C7333B6@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=xry111@xry111.site \
/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).