public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ishikawa at yk dot rim.or.jp" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109041] Bogus compile time check by __builtin_memset? error: ‘__builtin_memset’ writing 4 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=] Date: Wed, 08 Mar 2023 15:52:30 +0000 [thread overview] Message-ID: <bug-109041-4-elyZdzFHuz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109041-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109041 --- Comment #6 from ishikawa,chiaki <ishikawa at yk dot rim.or.jp> --- Created attachment 54610 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54610&action=edit The script to produce the warning in the original report with gcc-11. The source file needs to be in /tmp/sqlite3-preprocessed-2.c Run this script with bash this-script and it will print something like this on my linux PC. Here I put the script into t83.sh: bash ~/Dropbox/TB-DIR/WALL-PATCH-DIR/t83.sh /tmp/sqlite3-preprocessed-2.c: In function ‘posixUnlock’: /tmp/sqlite3-preprocessed-2.c:22632:42: error: self-comparison always evaluates to true [-Werror=tautological-compare] 22632 | sqlite3PendingByte+1==(sqlite3PendingByte+1) | ^~ In function ‘memset’, inlined from ‘pager_playback’ at /tmp/sqlite3-preprocessed-2.c:32113:4: /tmp/sqlite3-preprocessed-2.c:4273:10: error: ‘__builtin_memset’ writing 4 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=] 4273 | return __builtin___memset_chk (__dest, __ch, __len, __builtin_object_size (__dest, 0)); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /tmp/sqlite3-preprocessed-2.c: In function ‘pager_playback’: /tmp/sqlite3-preprocessed-2.c:32089:30: note: destination object ‘*pPager.pTmpSpace’ of size [0, 9223372036854775807] 32089 | zSuper = (void *) &pPager->pTmpSpace[4]; | ~~~~~~^~~~~~~~~~~ /tmp/sqlite3-preprocessed-2.c:32089:30: note: destination object ‘*pPager.pTmpSpace’ of size [0, 9223372036854775807] cc1: all warnings being treated as errors ishikawa@ip030:/NREF-COMM-CENTRAL/mozilla$
next prev parent reply other threads:[~2023-03-08 15:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-06 11:16 [Bug c/109041] New: " ishikawa at yk dot rim.or.jp 2023-03-06 16:40 ` [Bug tree-optimization/109041] " pinskia at gcc dot gnu.org 2023-03-07 15:52 ` ishikawa at yk dot rim.or.jp 2023-03-07 15:56 ` pinskia at gcc dot gnu.org 2023-03-08 1:14 ` pinskia at gcc dot gnu.org 2023-03-08 5:11 ` ishikawa at yk dot rim.or.jp 2023-03-08 10:02 ` marxin at gcc dot gnu.org 2023-03-08 15:52 ` ishikawa at yk dot rim.or.jp [this message] 2023-03-08 15:55 ` ishikawa at yk dot rim.or.jp 2023-03-09 11:09 ` marxin at gcc dot gnu.org 2023-03-10 14:49 ` ishikawa at yk dot rim.or.jp
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-109041-4-elyZdzFHuz@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).