From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5D603384AB5B; Tue, 7 May 2024 10:45:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5D603384AB5B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1715078709; bh=v2uDV9mxcct/1DhAVC02ZE7ql6uM6TsFA6utVtyTE44=; h=From:To:Subject:Date:In-Reply-To:References:From; b=y2WnDNmu2qiGbPWy3kh3dLBRQqU6uygGD3wVY1p8Gw56d8/+YEHPZvXtFAhvquE+L zhQ0eMHqBFjuW1g5fbzU8bFzuszUSJwXjl5fBrTniEKExZb306c1PCopnInDi3/IEB jj69Hlg5vxqQfyL2e/0AbThHCbJOWTp9pej+PTOQ= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114872] [13/14/15 Regression] Miscompilation with -O2 after commit r13-8037 Date: Tue, 07 May 2024 10:45:05 +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: 13.2.1 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.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: 13.3 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=3D114872 --- Comment #20 from Jakub Jelinek --- (In reply to Sergei Trofimovich from comment #18) > > 2) ideally show a gdb session with the important events, which setjmp w= as it (I see _setjmp and __sigsetjmp calls in the function), which exact fu= nction called from the function ended up aborting/doing longjmp in the sign= al handler and where is the crash Strange. If it is the _setjmp call on line 26315 followed by kill SIGABRT = from sig_error(); on the same line, then I don't see any local vars modified in between, except that int t on line 26315 inside of sig_GAP_Enter macro. There is then __sigsetjmp on line 26324, but no further kill calls and I th= ink this isn't in a loop.=