From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B30F33858D28; Mon, 30 Jan 2023 11:56:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B30F33858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675079806; bh=tI4WI74e9OkUzdI5y8aFGq8ndssX6dLkO4F8EL4OQBo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=WpxlJXDS3s7D491wDVcdqWqiWlfrEWJwooJ9wx6F2EYN5YLGxh9D4UtycwGuswVeq muMxu4wWBKceMw+8Z7+kkKpR8disMNkBStSZR+ZedT7iHArfVS3wb07RoQ/hFBNDz2 LaVnGjtcjHrk63O2aCJP95P9M+xvK+9TsAec++Yc= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108595] -fcall-saved-a1 with -O2 leads to incorrect RISC-V code-gen around inline assembly Date: Mon, 30 Jan 2023 11:56:46 +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: inline-asm, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia 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: --- 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=3D108595 --- Comment #2 from Andrew Pinski --- It is related to sibcalls and aarch64 with x1 has the same issue. I am suspecting this is just an invalid option to use here.=