From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7F6AF3857C5A; Mon, 9 Jan 2023 18:03:31 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7F6AF3857C5A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1673287411; bh=3AH5UwtDOZrPGc+lRbG/2AUlv8r1E/86KEVnE52XhlI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=w0dKleou5sL2sz2EoEyj+sLGpR7C8Lrv7IxSczDvdOUbTTGkcpjXiwuk7gO0r+Nc4 RJcN+ivqmGOw7xR+vQerQQUXpTCpifj3sOw1L65AFVVvSy4L0361iwJaPtK+z+Gee4 AYGJvSflOcVLzpTbAgV1TIp2yv/Cig8xLcq51+jA= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/108278] [13 Regression] runtime error with -O1 -Wall Date: Mon, 09 Jan 2023 18:03:31 +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: 13.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108278 --- Comment #17 from Jakub Jelinek --- We know the commit introduced UB on the compiler side, but what I don't understand is why it triggered on the testcases you've provided. It surely introduced UB when compiling libgcc/unwind-dw2.c or during predefining macr= os with -fbuilding-libgcc, but I think the problematic code with uninitialized array of poly_ints could happen at different times.=