From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 11DC43858D35; Tue, 27 Jun 2023 17:19:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 11DC43858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1687886391; bh=o8m1j8azw+oJXenxwopi/nbqTS+8TiKL7133DB9EsOE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gCsi8aoUx9FnAsexETuc+b0MpTk1Ebd5cJby/81qkZhCZ/UmJ8xALnxW4eBqrpAVp aekuy4KMWmtu3/VULWjAl4XaY0KtnbZPtVxa4knisbckKGfJ0qNEONjM/v0sBFQXZ6 67r/P27QxEGSbyMkIzvVFdk5H+ssx340msXP0DDg= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/110437] SIGILL when return missing in a C++ function with a condition Date: Tue, 27 Jun 2023 17:19:50 +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: 13.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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=3D110437 --- Comment #2 from Andrew Pinski --- >With gcc 12.2 at least the same code doesn't trigger SIGILL. Well in GCC 13+ at -O0 and -Og, GCC behavior changed from being fully undef= ined to be trapping for folks to try to catch instead of saying they were seeing= odd behavior. GCC 8+ changed the behavior to become unreachable: https://gcc.gnu.org/gcc-8/porting_to.html=