From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EC4993858CDA; Mon, 29 Jan 2024 22:16:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EC4993858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1706566610; bh=ukP60dGdB54W8o1sAXSuTofz2Vw6/H2p2nIRFCRDfvc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=saqIGtnnnDIU38lDa/9gp57GvOdVfjG8+NlfH6xVxDWpaQrASOOiMCf2vGVaZ7wPd LjTdSLGbhD8aGITlV/xHCGI0ECkgqD4qqYevrejlbQ0V/Sm/TirGskadIJWEFOegBT utm2GKbjcvfViNfCtLko1c/HyQUtFw+6bhcC3w3A= From: "stefan at bytereef dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113664] False positive warnings with -fno-strict-overflow (-Warray-bounds, -Wstringop-overflow) Date: Mon, 29 Jan 2024 22:16:50 +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: 14.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: stefan at bytereef dot org X-Bugzilla-Status: UNCONFIRMED 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=3D113664 --- Comment #2 from Stefan Krah --- Thanks for the explanation! I agree that one should not rely on -fno-strict-overflow. In this case, my project is "vendored" in CPython and they compile everything with -fno-strict-overflow, so it's out of my contro= l: https://github.com/python/cpython/issues/108562 mpdecimal itself does not need -fno-strict-overflow.=