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++/103939] New: memset with sizeof in wrong place not detected ? Date: Fri, 07 Jan 2022 11:21:33 +0000 [thread overview] Message-ID: <bug-103939-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103939 Bug ID: 103939 Summary: memset with sizeof in wrong place not detected ? Product: gcc Version: 12.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 this C++ code: $ more jan7d.cc #include <cstring> struct S { int a; int b; int c; int d; }; void f( S * ps) { memset(ps, sizeof(S), 0xff); } compiled with recent gcc trunk: $ /home/dcb/gcc/results/bin/gcc -c -g -O2 -Wall -Wextra -pedantic jan7d.cc $ compiled by clang-13: $ /usr/bin/clang++ -c -g -O2 -Wall -Wextra -pedantic jan7d.cc jan7d.cc:14:15: warning: setting buffer to a 'sizeof' expression; did you mean to transpose the last two arguments? [-Wmemset-transposed-args] memset(ps, sizeof(S), 0xff); ^ jan7d.cc:14:15: note: cast the second argument to 'int' to silence 1 warning generated.
next reply other threads:[~2022-01-07 11:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-07 11:21 dcb314 at hotmail dot com [this message] 2022-01-07 11:27 ` [Bug c++/103939] " redi at gcc dot gnu.org 2022-01-07 13:43 ` egallager at gcc dot gnu.org 2022-01-07 14:39 ` redi at gcc dot gnu.org 2022-01-07 14:42 ` redi at gcc dot gnu.org 2022-01-07 16:58 ` dcb314 at hotmail dot com 2022-01-07 17:34 ` redi at gcc dot gnu.org 2022-01-07 17:36 ` redi at gcc dot gnu.org 2022-01-07 17:38 ` jakub at gcc dot gnu.org 2022-01-07 17:54 ` redi at gcc dot gnu.org 2022-01-07 18:07 ` schwab@linux-m68k.org 2022-01-07 18:34 ` 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-103939-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).