public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "boris at kolpackov dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/115274] New: Bogus -Wstringop-overread in SQLite source code Date: Wed, 29 May 2024 12:07:08 +0000 [thread overview] Message-ID: <bug-115274-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115274 Bug ID: 115274 Summary: Bogus -Wstringop-overread in SQLite source code Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: boris at kolpackov dot net Target Milestone: --- Compiled attached sqlite3.c from recent SQLite release with GCC 14 and -O3 produces the following bogus (according to our analysis) warning: $ gcc-14 -O3 -c sqlite3.c In function ‘sqlite3Strlen30’, inlined from ‘sqlite3ColumnSetColl’ at sqlite3.c:115936:10: sqlite3.c:33361:28: warning: ‘strlen’ reading 1 or more bytes from a region of size 0 [-Wstringop-overread] 33361 | return 0x3fffffff & (int)strlen(z); | ^~~~~~~~~ In function ‘sqlite3ColumnSetColl’: cc1: note: source object is likely at address zero $ gcc-14 --version gcc-14 (Debian 14.1.0-1) 14.1.0 There is no such warning with GCC 13.2.0.
next reply other threads:[~2024-05-29 12:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-29 12:07 boris at kolpackov dot net [this message] 2024-05-29 12:08 ` [Bug tree-optimization/115274] " pinskia at gcc dot gnu.org 2024-05-29 12:15 ` boris at kolpackov dot net 2024-05-29 12:35 ` sjames at gcc dot gnu.org 2024-05-29 12:46 ` boris at kolpackov dot net 2024-06-28 20:41 ` pinskia at gcc dot gnu.org 2024-06-28 21:07 ` drh at sqlite dot org 2024-06-28 22:53 ` andi-gcc at firstfloor dot org 2024-06-28 22:57 ` andi-gcc at firstfloor dot org 2024-06-29 1:58 ` ak at gcc dot gnu.org 2024-06-29 15:57 ` andi-gcc at firstfloor dot 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-115274-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).