From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 273F93839422; Thu, 12 Aug 2021 21:05:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 273F93839422 From: "quentin at armitage dot org.uk" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101451] Incorrect -Wstringop-truncation warning Date: Thu, 12 Aug 2021 21:05:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 11.1.1 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: quentin at armitage dot org.uk X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2021 21:05:48 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D101451 --- Comment #5 from Quentin Armitage --- In the code of my original example (which I have simplified) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D #include static char dest[16]; static char src[16] =3D "012345678901234"; int main(__attribute__(void) { do { dest[0] =3D '\0'; strncat(dest, src, sizeof(dest) - 1); } while (0); } =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D there is no truncation since 15 bytes are copied to dest, with a NUL byte added, and the maximum length of a string in src is 15 bytes plus terminati= ng NUL byte. Also, the warning is not generated if -O2 is not specified, but it is gener= ated if -O2 is specified (-O1 does not generate the warning). To me this doesn't seem right.=