From: "H. Peter Anvin" <hpa@zytor.com>
To: Jakub Jelinek <jakub@redhat.com>, Andy Lutomirski <luto@kernel.org>
Cc: gcc@gcc.gnu.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vladimir Makarov <vmakarov@redhat.com>
Subject: Re: gcc feature request / RFC: extra clobbered regs
Date: Tue, 30 Jun 2015 14:41:56 -0700 [thread overview]
Message-ID: <55930D24.4040105@zytor.com> (raw)
In-Reply-To: <20150630213736.GQ10247@tucnak.redhat.com>
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.
-hpa
next prev parent reply other threads:[~2015-06-30 21:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 21:22 gcc feature request / RFC: extra clobbered regs Andy Lutomirski
2015-06-30 21:32 ` H. Peter Anvin
2015-06-30 21:37 ` Jakub Jelinek
2015-06-30 21:41 ` H. Peter Anvin [this message]
2015-06-30 21:48 ` Andy Lutomirski
2015-06-30 21:52 ` H. Peter Anvin
2015-06-30 21:55 ` Andy Lutomirski
2015-06-30 22:02 ` H. Peter Anvin
2015-07-01 4:20 ` Jeff Law
2015-07-01 15:23 ` Vladimir Makarov
2015-07-01 15:27 ` Andy Lutomirski
2015-07-01 17:57 ` Vladimir Makarov
2015-07-01 15:31 ` Jakub Jelinek
2015-07-01 17:35 ` Vladimir Makarov
2015-07-01 17:38 ` Andy Lutomirski
2015-07-01 17:43 ` Jakub Jelinek
2015-07-01 18:12 ` Vladimir Makarov
2015-07-01 20:09 ` Andy Lutomirski
2015-07-02 6:16 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55930D24.4040105@zytor.com \
--to=hpa@zytor.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vmakarov@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox