From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B08793858C39; Thu, 29 Feb 2024 23:03:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B08793858C39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709247817; bh=0u5Z6a2LVN+QPD4ffaugkLeUkD6L7m9DLsAE88Ugevs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=IAFH7CAE4MqTh0lOGckY3ql7WpSASveQb6ckUy4HQV7fdiV+Fcum2YN/l5xzih0n6 Jx7QO8yaH7qQJNf7xrba3rnvD44umpA/Z2szsH22mU4a49kUC8IqqITAM7z43YALSX 3orFalgbZXEyO3W05QOrdMdJmeYxx8gnUX0YEc4U= From: "evan.teran at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114178] incorrect -Wstringop-overflow with freestanding + new w/ initialization + no sse Date: Thu, 29 Feb 2024 23:03:37 +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: 13.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: evan.teran at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D114178 --- Comment #4 from Evan Teran --- @Andrew, thanks for the quick analysis! Just to confirm, the warning is in = fact incorrect and the emitted code is not stomping outside of the buffer bounds? I ask because I did also one last bit, which is that changing the buffer si= ze can make the warning go away. That is if I make the buffer in the example something like 132, then it's happy again, which at the very least, makes me wonder if the vectorized code is in fact going out of bounds when the size doesn't align with the vectorized code's expectations.=