public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "benh at kernel dot crashing.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/56314] Please allow per-function specification of register conventions
Date: Fri, 15 Feb 2013 06:52:00 -0000 [thread overview]
Message-ID: <bug-56314-4-EQqaqqIdZU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56314-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56314
benh at kernel dot crashing.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |benh at kernel dot
| |crashing.org
--- Comment #4 from benh at kernel dot crashing.org 2013-02-15 06:52:31 UTC ---
I would definitely like to see that on powerpc as well.
A typical usage case for Linux is inline functions intended as a fast path
(such as spin lock) for which we want to be able to branch to an unlikely slow
path (contention case, timeout case, error case...) while limiting the impact
on the caller.
next prev parent reply other threads:[~2013-02-15 6:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 1:56 [Bug other/56314] New: " hpa at zytor dot com
2013-02-14 2:04 ` [Bug other/56314] " pinskia at gcc dot gnu.org
2013-02-14 2:24 ` hpa at zytor dot com
2013-02-14 10:29 ` [Bug middle-end/56314] " rguenth at gcc dot gnu.org
2013-02-15 6:52 ` benh at kernel dot crashing.org [this message]
2013-02-15 6:56 ` pinskia at gcc dot gnu.org
2022-10-03 16:20 ` hpa at zytor dot com
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=bug-56314-4-EQqaqqIdZU@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).