From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C83133858D28; Mon, 14 Mar 2022 17:35:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C83133858D28 From: "msebor at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/104789] [12 Regression] -Wstringop-overflow false positive at -O3 for an unrolled loop Date: Mon, 14 Mar 2022 17:35:22 +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: 12.0 X-Bugzilla-Keywords: diagnostic, missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: msebor 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: 12.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: Mon, 14 Mar 2022 17:35:22 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104789 --- Comment #11 from Martin Sebor --- The direct store subset of -Wstringop-overflow that runs in the strlen pass (i.e., those handled in strlen_pass::handle_store) might be better handled = in VRP and issued under -Warray-bounds. The challenge there is that unlike th= is -Wstringop-overflow subset which respects subobject boundaries, -Warray-bou= nds intentionally considers complete objects (this was done to avoid false positives). So before moving all of strlen a solution to consider is to merge these two sets of warnings while preserving the subobject sensitivity. Another (indirectly related) improvement is to also move -Warray-bounds out= of VRP and into the access warning pass, and run it at the same times as most other warnings there (that would also enable -Warray-bounds at -O0, which m= ight of course trigger some new false positives).=