public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104594] narrowing of -1 to unsigned char not detected with requires concepts Date: Fri, 18 Feb 2022 09:28:36 +0000 [thread overview] Message-ID: <bug-104594-4-Q3g9GoyEat@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104594-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104594 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2022-02-18 Summary|narrowing conversion of -1 |narrowing of -1 to unsigned |to unsigned char at compile |char not detected with |time not detected |requires concepts Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. GCC correctly detects: template <unsigned char DIM_FROM> constexpr bool Geometry = (DIM_FROM == -1); template <class INIT> constexpr bool tt1 = Geometry<INIT::n>; template<int N> struct X { static constexpr int n = N; }; bool t = tt1<X<-1>>;
next prev parent reply other threads:[~2022-02-18 9:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-18 9:15 [Bug c++/104594] New: narrowing conversion of -1 to unsigned char at compile time not detected raffael at casagrande dot ch 2022-02-18 9:28 ` pinskia at gcc dot gnu.org [this message] 2022-02-28 17:43 ` [Bug c++/104594] narrowing of -1 to unsigned char not detected with requires concepts ppalka at gcc dot gnu.org 2022-04-06 22:31 ` ppalka at gcc dot gnu.org 2022-04-06 22:42 ` ppalka at gcc dot gnu.org 2022-04-06 22:55 ` ppalka at gcc dot gnu.org 2022-04-06 22:57 ` ppalka at gcc dot gnu.org 2022-04-07 1:53 ` jason at gcc dot gnu.org 2024-01-19 18:35 ` cvs-commit at gcc dot gnu.org 2024-01-19 18:40 ` jason 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-104594-4-Q3g9GoyEat@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).