From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 559B73858D28; Wed, 25 Jan 2023 17:45:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 559B73858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674668730; bh=lUwKFy+i3xBQFxKUjIunx2lf0Xb7xlPGaOObRl2VSok=; h=From:To:Subject:Date:In-Reply-To:References:From; b=fU3BWaiB7nuVfu5lsVmD6oj+zNa/tngQ7DnqJ7ZK5NDhb8U8wkKZlI6/6XPrNHreQ 3s2bGa0gnt83xta4bZPQiWkTt+K8wX4bV4qizcRkv11NRmKP+TO867+98bsowKiHCi G8qTbnxoAvyJqx2USti6bgBL4/2qkvK5uOt4UOP4= From: "rearnsha at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100000] non-leaf epologue/prologue used if MVE v4sf is used for load/return Date: Wed, 25 Jan 2023 17:45:29 +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: 11.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: enhancement X-Bugzilla-Who: rearnsha 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: --- 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=3D100000 --- Comment #2 from Richard Earnshaw --- If the testcase is built with -march=3Darmv8.1-m.main+mve.fp then the usele= ss stack adjustments go away. I think that's because V4SFmode is not a suppor= ted vector mode for integer MVE - see arm_vector_mode_supported_p() in arm.cc.= =20 When it isn't a builtin type we end up with a BLKmode object that the compi= ler creates a stack-slot for, even though no RTL is ever generated to use the s= lot in this case.=