public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "richard.yao at alumni dot stonybrook.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/98801] Request for a conditional move built-in function Date: Sat, 27 May 2023 17:56:58 +0000 [thread overview] Message-ID: <bug-98801-4-atEEkxE4BP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98801-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98801 Richard Yao <richard.yao at alumni dot stonybrook.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard.yao at alumni dot stonybro | |ok.edu --- Comment #8 from Richard Yao <richard.yao at alumni dot stonybrook.edu> --- I just filed #110007 to ask for __builtin_unpredictable(). Something like __builtin_unpredictable(condition) ? a : b should be equivalent to a __builtin_cmov(). __builtin_unpredictable() is already implemented in Clang (although it does not yet pass it to the backend), so adopting it would be preferable to implementing an entirely new builtin.
prev parent reply other threads:[~2023-05-27 17:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-23 4:47 [Bug c++/98801] New: " jeffhurchalla at gmail dot com 2021-01-23 6:53 ` [Bug c++/98801] " pinskia at gcc dot gnu.org 2021-01-23 19:37 ` jeffhurchalla at gmail dot com 2021-01-23 20:28 ` jeffhurchalla at gmail dot com 2021-01-25 9:36 ` [Bug middle-end/98801] " rguenth at gcc dot gnu.org 2021-01-25 19:19 ` peter at cordes dot ca 2021-01-26 0:17 ` jeffhurchalla at gmail dot com 2021-01-27 5:18 ` jeffhurchalla at gmail dot com 2023-05-27 17:56 ` richard.yao at alumni dot stonybrook.edu [this message]
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=bug-98801-4-atEEkxE4BP@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).