From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 11F693857838; Mon, 6 Mar 2023 20:20:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 11F693857838 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1678134023; bh=LwUROm8+0yqo3uT+37mDAdfB7xV3EVr9wx1u323hFrg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Kyy0l6FHjFXtzpftHSADqxZJTGp+8klwRe+3xWEizhPGtK4HnM7EgGekQhYO9C21q 37iqggjVDhDfj4FLs1ayN3AdDided2yzpJgbgroP+44OaMRYFAZ9sciZG86l30MbZr 8JmSEaCUFvdx9odTPVTvAgQ/9yvUrrqg51oyQgLw= From: "amonakov at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108315] -mcpu=power10 changes ABI Date: Mon, 06 Mar 2023 20:20:20 +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: 13.0 X-Bugzilla-Keywords: ABI, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: amonakov 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=3D108315 --- Comment #18 from Alexander Monakov --- It seems you are saying that as long as GCC emits code according to the Holy Scripture that is the ABI spec, everything is fine. I imagine on other architectures maintainers are able to consider how the whole toolchain works together to avoid leaving the user with difficult-to-debug fallout.=