public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jlame646 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114237] New: GCC emits no narrowing conversion warning when call is made indirectly through std::invoke Date: Tue, 05 Mar 2024 12:34:10 +0000 [thread overview] Message-ID: <bug-114237-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114237 Bug ID: 114237 Summary: GCC emits no narrowing conversion warning when call is made indirectly through std::invoke Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jlame646 at gmail dot com Target Milestone: --- Gcc emits no narrowing conversion warning for the following program. Only msvc emits the warning. https://godbolt.org/z/EPKv9fdWr ``` void expectsInt32(int32_t) { /* … */ } template<typename Func, typename Arg> void call(Func func, Arg arg) { std::invoke(func, arg); // arg is size_t, potentially causing narrowing conversion } int main() { size_t largeNumber = 4294967295; // Maximum value for uint32_t call(expectsInt32, largeNumber); // Compiles without warning in GCC/Clang with -Wconversion return 0; } ``` Even with -Wconversion and other flags as shown in the demo, no warning is emitted by gcc and clang.
next reply other threads:[~2024-03-05 12:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-05 12:34 jlame646 at gmail dot com [this message] 2024-03-05 14:28 ` [Bug c++/114237] " redi at gcc dot gnu.org 2024-03-05 14:29 ` redi 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-114237-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).