From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D17B4385840D; Wed, 25 Oct 2023 11:19:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D17B4385840D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1698232780; bh=Ra0L02pebREggAOUuh2mnanPNX0AhqGUF2iYrLEvv2s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=sLXxZOSjAlnfgGULaKYqz0SBlgGv1DP5Xoam5sBeBJxCjiJrb4F1zhNhJ/uURAN4w tqXWqNPfwu+VJpn31ltL+fF5fMD85CLRCGywbUTlUzfAecT6L1uhP0NJPJ2IxgIvfG xM8SljRYNlLlFu5Aka4oGTV0Cqosh46R5O+Myvac= From: "acoplan at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111677] [12/13/14 Regression] darktable build on aarch64 fails with unrecognizable insn due to -fstack-protector changes Date: Wed, 25 Oct 2023 11:19:39 +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, needs-bisection X-Bugzilla-Severity: normal X-Bugzilla-Who: acoplan at gcc dot gnu.org 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: 12.4 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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=3D111677 Alex Coplan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rsandifo at gcc dot gnu.org --- Comment #13 from Alex Coplan --- The problem seems to be this code in aarch64_process_components: while (regno !=3D last_regno) { bool frame_related_p =3D aarch64_emit_cfi_for_reg_p (regno); machine_mode mode =3D aarch64_reg_save_mode (regno); rtx reg =3D gen_rtx_REG (mode, regno); poly_int64 offset =3D frame.reg_offset[regno]; if (frame_pointer_needed) offset -=3D frame.bytes_below_hard_fp; rtx addr =3D plus_constant (Pmode, ptr_reg, offset); rtx mem =3D gen_frame_mem (mode, addr); which emits a TFmode mem with offset 512, which is out of range for TFmode = (so we later ICE with an unrecognisable insn). Presumably this just needs twea= king to emit a new base anchor in the case of large offsets like this. It looks like the code in aarch64_save_callee_saves already does this.=