From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22932 invoked by alias); 12 Mar 2018 14:27:36 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 22236 invoked by uid 89); 12 Mar 2018 14:27:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy= X-HELO: foss.arm.com Received: from foss.arm.com (HELO foss.arm.com) (217.140.101.70) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 12 Mar 2018 14:27:34 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id C48DE1596; Mon, 12 Mar 2018 07:27:32 -0700 (PDT) Received: from localhost (unknown [10.32.99.72]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 6855C3F24A; Mon, 12 Mar 2018 07:27:31 -0700 (PDT) From: Richard Sandiford To: Wilco Dijkstra Mail-Followup-To: Wilco Dijkstra ,James Greenhalgh , GCC Patches , Richard Earnshaw , Ramana Radhakrishnan , nd , richard.sandiford@arm.com Cc: James Greenhalgh , GCC Patches , Richard Earnshaw , Ramana Radhakrishnan , nd Subject: Re: [PATCH][AArch64] Remove aarch64_frame_pointer_required References: <20171107170512.GA30919@arm.com> <87muzryjs7.fsf@e105548-lin.cambridge.arm.com> Date: Mon, 12 Mar 2018 14:27:00 -0000 In-Reply-To: (Wilco Dijkstra's message of "Thu, 1 Mar 2018 20:21:32 +0000") Message-ID: <87k1uhgyib.fsf@e105548-lin.cambridge.arm.com> User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SW-Source: 2018-03/txt/msg00529.txt.bz2 Wilco Dijkstra writes: > Richard Sandiford wrote: >> But there's the third question of whether the frame pointer is available >> for general allocation.=C2=A0 By removing frame_pointer_required, we're = saying >> that the frame pointer is always available for general use.=C2=A0=20 > > Unlike on ARM/Thumb-2, the frame pointer is unfortunately never available= for > general allocation on AArch64 - so we cannot use it for something > actually useful. > A while back there were mid-end patches proposed to allow general allocat= ion > of FP but those weren't accepted. Ah, missed that, sorry. So the asm example I gave probably is as far as the "problem" goes, and the argument can be made that that's just doing what the user asked for. Sorry for the noise... Richard