public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109056] New: cppcheck: no warning for suspicious return type Date: Tue, 07 Mar 2023 16:50:14 +0000 [thread overview] Message-ID: <bug-109056-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109056 Bug ID: 109056 Summary: cppcheck: no warning for suspicious return type Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- For the following C code: unsigned long f( int n) { return n * 1000; } where the programmer may have intended using an unsigned long constant like 1000UL, then static analyser cppcheck can be made to say: mar7b.cc:4:2: style: int result is returned as long value. If the return value is long to avoid loss of information, then you have loss of information. [truncLongCastReturn] return n * 1000; gcc says nothing: $ ~/gcc/results/bin/gcc -c -g -O2 -Wall -Wextra mar7b.cc $ The example code is derived from 10 examples in the source code of linux-6.3-rc1, so the problem does really occur in practice.
next reply other threads:[~2023-03-07 16:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-07 16:50 dcb314 at hotmail dot com [this message] 2023-03-07 16:56 ` [Bug c/109056] " pinskia at gcc dot gnu.org 2023-03-07 16:56 ` pinskia at gcc dot gnu.org 2023-03-07 17:03 ` dcb314 at hotmail dot com
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-109056-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).