public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <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: Mon, 25 Jan 2021 09:36:31 +0000 [thread overview] Message-ID: <bug-98801-4-Gohtsze0ns@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 Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c++ |middle-end Severity|normal |enhancement Last reconfirmed| |2021-01-25 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Slight complication arises because people will want to have cmoves with a memory destination. So possibly void __builtin_cmov (T *dest, bool, T, T, void *); preferably usable in a type-generic way. The void * is at least internally required to carry type-based alias info of the destination. That won't solve the eventual request to have cmov _from_ memory ... (if we leave all of the memory combining to RTL people will again complain that it's subject to compilers discretion).
next prev parent reply other threads:[~2021-01-25 9:36 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 ` rguenth at gcc dot gnu.org [this message] 2021-01-25 19:19 ` [Bug middle-end/98801] " 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
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-Gohtsze0ns@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).