public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "raffael at casagrande dot ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/104594] New: narrowing conversion of -1 to unsigned char at compile time not detected Date: Fri, 18 Feb 2022 09:15:49 +0000 [thread overview] Message-ID: <bug-104594-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104594 Bug ID: 104594 Summary: narrowing conversion of -1 to unsigned char at compile time not detected Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: raffael at casagrande dot ch Target Milestone: --- The current gcc trunk compiles the following piece of code: ------------------------------------------------------------ template <unsigned char DIM_FROM> concept Geometry = (DIM_FROM == -1); template <class INIT> requires Geometry<INIT::n> auto GaussNewton(const INIT& init) -> void {} template<int N> struct X { static constexpr int n = N; }; int main() { GaussNewton(X<-1>{}); } -------------------------------------- I think this should NOT compile since it entails a narrowing conversion of -1 to an unsigned char type at compile time. Clang as well as MSVC fail to compile the code. (In many other cases, gcc also fails to compile if such a narrowing conversion happens at compile time.)
next reply other threads:[~2022-02-18 9:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-18 9:15 raffael at casagrande dot ch [this message] 2022-02-18 9:28 ` [Bug c++/104594] narrowing of -1 to unsigned char not detected with requires concepts pinskia at gcc dot gnu.org 2022-02-28 17:43 ` 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@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).