From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E2A493858D28; Thu, 28 Dec 2023 17:38:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E2A493858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1703785080; bh=vbBShxJ8PRmIsEt2OB6R8OQWU1qHg2Y0IjLPir7ZGPs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=j43OvM/+W98h4sSiIa8V4J8Myi6THhj+qRnihZnKJmioB+iWZCLimf3/s73DLbKR+ k/AhsgIP0lLJ5CDGQVhMPJ7XAgDZkAKKLBgemJItyXc1W1xjivEoamIiUToyW+v6O3 baxEdQL//VNIrvwTgVLB4nyhS3D6KsO4kSXVhfPw= From: "mikpelinux at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110934] m68k: ICE with -fzero-call-used-regs=all compiling openssh 9.3p2 Date: Thu, 28 Dec 2023 17:38:00 +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.2.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: mikpelinux at gmail dot com X-Bugzilla-Status: NEW 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=3D110934 --- Comment #8 from Mikael Pettersson --- The generic code synthesizes a move from CONST0_RTX (XFmode) to an XFmode FP reg, and that causes the ice. Forcing the mode of both to SFmode or DFmode avoids the ice and generates sane-looking code. The XFmode comes from the generic code's use of regno_reg_rtx[regno] (in zcur_select_mode_rtx). I'm not sure if overriding TARGET_ZERO_CALL_USED_REGS on m68k is the right thing to do, or if it only masks a deeper problem within the backend.=