public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "georgmueller at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103173] strncpy output may be truncated copying 32 bytes from a string of length 1439 (bogus) [-Werror=stringop-truncation] Date: Thu, 20 Jul 2023 08:48:25 +0000 [thread overview] Message-ID: <bug-103173-4-0QeKQ9wFce@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103173-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103173 Georg Müller <georgmueller at gmx dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |georgmueller at gmx dot net --- Comment #5 from Georg Müller <georgmueller at gmx dot net> --- The problem in comment #3 is still valid vor gcc 13.1.1 (testes using gcc-13.1.1-4.fc38.x86_64 on Fedora 38). The warning disappears if I add a variable "int x" into the first place of struct user_data. The compiler seems to mix up the struct size and size of a member if they point to the same memory address...
prev parent reply other threads:[~2023-07-20 8:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-10 15:40 [Bug tree-optimization/103173] New: " patrickdepinguin at gmail dot com 2021-11-10 19:17 ` [Bug tree-optimization/103173] " msebor at gcc dot gnu.org 2021-11-11 9:15 ` rguenth at gcc dot gnu.org 2021-12-21 15:26 ` patrickdepinguin at gmail dot com 2021-12-21 15:35 ` patrickdepinguin at gmail dot com 2023-07-20 8:48 ` georgmueller at gmx dot net [this message]
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-103173-4-0QeKQ9wFce@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).