From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A8F873858D35; Wed, 18 Jan 2023 06:38:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A8F873858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674023897; bh=jhr2QJdXSnKQ7iNOsZ9hCs5KRWa/2JiDWpVAbKRovP0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JOZDRs2OkPOGMKEC5jfKDTj1SeEkTZ63ASmxHC/8mGzKhFAWTPPD50cOTqcGqWWWi 5lKoTDHGV2qTloV6TlweIitblgaXHOItkzBuipS+xLmPiuwGkEufxDzEbi20tCp6If 5JoqMGMvAJYkT5Wew+fEJMW0o2GDzOfqAFiXELqQ= From: "linkw at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108415] ICE in emit_library_call_value_1 at gcc/calls.cc:4181 Date: Wed, 18 Jan 2023 06:38:17 +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: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: linkw at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 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=3D108415 --- Comment #4 from Kewen Lin --- (In reply to Peter Bergner from comment #3) > (In reply to Kewen Lin from comment #2) > > The contradictory thing is that we can have TARGET_VSX and TARGET_SOFT_= FLOAT > > (!TARGET_HARD_FLOAT) together with the proposed option combination. :) >=20 > I'm not sure what you mean with this comment, but just to be clear, we > should not allow TARGET_VSX and TARGET_SFT_FLOAT (!TARGET_HARD_FLOAT) at = the > same time. Sorry for the confusion and thanks for clarifying, I meant the similar mean= ing that: the given option combination, like -mmodulo -mcpu=3D401 or -mcpu=3D401 -mpower9-vector or ... makes us to have both TARGET_VSX and TARGET_SOFT_FLOAT at the same time, it= 's contradictory (shouldn't be allowed as you noted).=