public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sworddragon2 at aol dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/55896] New: Annoying compiler warning Date: Mon, 07 Jan 2013 13:48:00 -0000 [thread overview] Message-ID: <bug-55896-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55896 Bug #: 55896 Summary: Annoying compiler warning Classification: Unclassified Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: sworddragon2@aol.com Created attachment 29097 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29097 Example code After changing a global struct to a static variable I got a compiler warning. I have analyzed this and tried to produce a minimum testcase. In the attachments is an example code and compiling it with "gcc -O3 -Wall -Wextra -o test -pedantic test.c" will result in the following warning: In file included from /usr/include/string.h:638:0, from test.c:3: In function 'strncat', inlined from 'load_app_settings' at test.c:39:10: /usr/include/x86_64-linux-gnu/bits/string3.h:150:3: warning: call to __builtin___strncat_chk might overflow destination buffer [enabled by default] Removing static from "static struct status STATUS;" solves the problem. Any random change in load_app_settings() can solve the problem too even if the change has nothing to do with the problem. For example if "strncat(content_2, content_1, w_strlen(content_1) - 1);" is changed to "strncat(content_2, content_1, w_strlen(content_1));" or " && content_1[0] == '['" is removed in the condition.
next reply other threads:[~2013-01-07 13:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-07 13:48 sworddragon2 at aol dot com [this message] 2014-03-18 11:21 ` [Bug c/55896] " mpolacek at gcc dot gnu.org 2014-03-18 11:38 ` jakub at gcc dot gnu.org 2014-03-18 12:11 ` jakub at gcc dot gnu.org 2014-03-18 13:57 ` mpolacek at gcc dot gnu.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-55896-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).