From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EAA8D385800A; Tue, 5 Jan 2021 17:31:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EAA8D385800A From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/98503] [11 regression] -Warray-bounds false positive with global variables at -O2 since r11-3306-g3f9a497d1b0dd9da Date: Tue, 05 Jan 2021 17:31:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.0 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: Tue, 05 Jan 2021 17:31:25 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D98503 --- Comment #10 from Martin Sebor --- The main purpose of the "partly outside" warning is to detect reads/writes = that cross the trailing array boundary. Those typically come up when a "typeles= s" buffer (either char array or one allocated by a function like malloc) is us= ed to store a sequence of heterogeneous elements. Besides these bugs the warn= ing also detects other kinds of invalid accesses that span the boundary, like in comment #0. The access there in invalid for a different reason than the us= ual -Warray-bounds, so issuing a warning that's controlled by a different option would be appropriate (-Wstrict-aliasing seems like a good fit). It's somet= hing we have discussed doing but it's not at the top my to do list. Making it conditional on -fstrict-aliasing might be worth considering as well.=