public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107065] GCC treats rvalue as an lvalue Date: Wed, 28 Sep 2022 12:00:25 +0000 [thread overview] Message-ID: <bug-107065-4-1bGQynvoDT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107065-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107065 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2022-09-28 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Reduced to remove the library dependency: enum Cat { prvalue, lvalue, xvalue }; template<typename T> struct value_category { // Or can be an integral or enum value static constexpr auto value = prvalue; }; template<typename T> struct value_category<T&> { static constexpr auto value = lvalue; }; template<typename T> struct value_category<T&&> { static constexpr auto value = xvalue; }; // Double parens for ensuring we inspect an expression, // not an entity #define VALUE_CATEGORY(expr) value_category<decltype((expr))>::value constexpr bool global = true; static_assert( VALUE_CATEGORY(!(!global)) == prvalue, "GCC gets this right" ); int main() { bool b = true; if ( VALUE_CATEGORY(!(!b)) != prvalue ) throw 1; }
next prev parent reply other threads:[~2022-09-28 12:00 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-28 7:35 [Bug c++/107065] New: GCC treats rvalue like lvalue jlame646 at gmail dot com 2022-09-28 12:00 ` redi at gcc dot gnu.org [this message] 2022-09-28 12:06 ` [Bug c++/107065] GCC treats rvalue as an lvalue jlame646 at gmail dot com 2022-09-28 12:09 ` jlame646 at gmail dot com 2022-09-28 12:50 ` redi at gcc dot gnu.org 2022-09-28 13:41 ` mpolacek at gcc dot gnu.org 2022-09-28 14:32 ` jlame646 at gmail dot com 2022-09-28 15:34 ` mpolacek at gcc dot gnu.org 2022-09-29 18:24 ` glisse at gcc dot gnu.org 2022-09-29 19:01 ` jakub at gcc dot gnu.org 2022-09-30 7:12 ` jakub at gcc dot gnu.org 2022-09-30 7:13 ` jakub at gcc dot gnu.org 2022-09-30 8:03 ` glisse at gcc dot gnu.org 2022-09-30 8:27 ` jakub at gcc dot gnu.org 2022-09-30 8:47 ` glisse at gcc dot gnu.org 2022-12-15 18:18 ` cvs-commit at gcc dot gnu.org 2022-12-16 9:23 ` jakub at gcc dot gnu.org 2023-02-10 17:44 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:12 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:19 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:20 ` jakub at gcc dot gnu.org
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-107065-4-1bGQynvoDT@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).