From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8E3C03858C60; Fri, 28 Apr 2023 12:12:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8E3C03858C60 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1682683929; bh=uVaRb798V/XtlAK0OtDO+UZGGX043kmlUizwGfNzD6g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jFyTYKfyMZoRBO7wDjVy8VAii07NudTsqJn7eNz4GbmhFhoEg3EhENKdnhrR680N0 WEgSh9f00f5VnnuTX2jIaMs9ixxoygcguDuRkeM4ACB4gCfHWwktbUTDiAo+zT8QAO AHKxy9oF173cOS6uexnhzRalFAAwBMK5amddIYRY= From: "paul.groke at dynatrace dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109665] Incorrect code generation for s390/s390x try-catch (__cxa_begin_catch), causing SIGSEGV Date: Fri, 28 Apr 2023 12:12:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: EH, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: paul.groke at dynatrace dot com 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=3D109665 --- Comment #2 from Paul Groke --- -fno-schedule-insns and/or -fno-schedule-insns2 don't change the instruction sequence for calling __cxa_begin_catch. BTW: for compiler versions present there, it's super easy to check this with godbolt.org. Just enter the compiler switches into the text-field next to t= he compiler selection control.=