Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752983AbbF3Vxo (ORCPT ); Tue, 30 Jun 2015 17:53:44 -0400 Received: from terminus.zytor.com ([198.137.202.10]:48684 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753258AbbF3Vxe (ORCPT ); Tue, 30 Jun 2015 17:53:34 -0400 Message-ID: <55930FB9.2070904@zytor.com> Date: Tue, 30 Jun 2015 14:52:57 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Andy Lutomirski CC: Jakub Jelinek , Andy Lutomirski , gcc@gcc.gnu.org, "linux-kernel@vger.kernel.org" , Linus Torvalds , Ingo Molnar , Thomas Gleixner , Vladimir Makarov Subject: Re: gcc feature request / RFC: extra clobbered regs References: <20150630213736.GQ10247@tucnak.redhat.com> <55930D24.4040105@zytor.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1399 Lines: 35 On 06/30/2015 02:48 PM, Andy Lutomirski wrote: > On Tue, Jun 30, 2015 at 2:41 PM, H. Peter Anvin wrote: >> On 06/30/2015 02:37 PM, Jakub Jelinek wrote: >>> I'd say the most natural API for this would be to allow >>> f{fixed,call-{used,saved}}-REG in target attribute. >> >> Either that or >> >> __attribute__((fixed(rbp,rcx),used(rax,rbx),saved(r11))) >> >> ... just to be shorter. Either way, I would consider this to be >> desirable -- I have myself used this to good effect in a past life >> (*cough* Transmeta *cough*) -- but not a high priority feature. > > I think I mean the per-function equivalent of -fcall-used-reg, so > hpa's "used" suggestion would do the trick. > > I guess that clobbering the frame pointer is a non-starter, but five > out of six isn't so bad. It would be nice to error out instead of > producing "disastrous results", though, if another bad reg is chosen. > (Presumably the PIC register on PIC builds would be an example of > that.) > Clobbering the frame pointer is perfectly fine, as is the PIC register. However, gcc might need to handle them as "fixed" rather than "clobbered". -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/