From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 42D03395CCB4; Thu, 14 May 2020 19:25:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 42D03395CCB4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1589484352; bh=JCUk9DfHGm+KVvbkPaMbpMk8n7DUmgXzgeBsrC2UZG8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eLGfOWIBXkeflX8VvekFnAwbJAh+ti7lGuDsI9xahAJGhq9bTqlUN/WeBOzWu9wD+ 5N2Bhc+VbvLrf3iZPBVdk2odbw1g1bcu0qcNgN3MfybsmD3ND+61tHqUW16zbcF0bw bxIPaZUXavprIOU6Wc4n2qMMKWEBuXhaNUFW6Qmo= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/95140] [10/11 Regression] bogus -Wstringop-overflow for a loop unrolled past the end of a trailing array Date: Thu, 14 May 2020 19:25:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: diagnostic, missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org 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 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, 14 May 2020 19:25:52 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95140 --- Comment #3 from Jakub Jelinek --- The warning should change, not the conservative assumption. There is a lot= of code in the wild with such trailing arrays, not everything uses flexible ar= ray members, [0] or [1] for that.=