From: Andreas Schwab <schwab@linux-m68k.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: James Tirta Halim <tirtajames45@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] ftw.c: Use unlikely for unlikely taken branches such that taken ones are placed closer
Date: Tue, 03 Oct 2023 09:47:40 +0200 [thread overview]
Message-ID: <87il7op2oz.fsf@linux-m68k.org> (raw)
In-Reply-To: <a17a00d539ae12a681885bd4bb21961e62bce093.camel@xry111.site> (Xi Ruoyao's message of "Tue, 03 Oct 2023 14:28:44 +0800")
On Okt 03 2023, Xi Ruoyao wrote:
> (what's the difference between __glibc_unlikely and glibc_unlikely)?
The difference is that the latter does not exist.
--
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."
next prev parent reply other threads:[~2023-10-03 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 3:40 James Tirta Halim
2023-10-03 6:28 ` Xi Ruoyao
2023-10-03 7:47 ` Andreas Schwab [this message]
2023-10-03 10:44 Wilco Dijkstra
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=87il7op2oz.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=libc-alpha@sourceware.org \
--cc=tirtajames45@gmail.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).