From: Jeff Law <law@redhat.com>
To: Helge Deller <deller@gmx.de>, John David Anglin <dave.anglin@bell.net>
Cc: "linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>
Subject: Re: Change call ABI on PA-RISC
Date: Mon, 14 Nov 2016 01:21:45 -0700 [thread overview]
Message-ID: <06f2cef7-6946-911e-53d8-375637d54096@redhat.com> (raw)
In-Reply-To: <2d705201-5651-b4e7-9e92-6d0f175b44b9@gmx.de>
On 11/13/2016 12:48 PM, Helge Deller wrote:
> On 13.11.2016 19:56, Jeff Law wrote:
>> On 11/13/2016 11:37 AM, Helge Deller wrote:
>>> If you are going to change the ABI, maybe we can add more things as well?
>>> Which comes to my mind here is for example an optimized mcount() function
>>> which allows changing the return pointer (see -mmcount-ra-address on MIPS) ?
>
>> As in twiddling RP to return to a different point?
>
> No, that's not the use case for me.
>
> I was working on the ftrace functionality in the Linux kernel.
> I'd need to look up the full details again, but as far as I remember one of
> the tracers wants to know the function to which the caller of mcount() would return,
> so some kind of simple __builtin_return_address(2).
Ah. Isn't that going to be sitting at sp-20 or something like that. My
PA is rusty, but my recollection is that's supposed to be at a fixed
location in the frame.
jeff
next prev parent reply other threads:[~2016-11-14 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 18:00 Change call ABI on PA-RISC John David Anglin
2016-11-13 18:37 ` Helge Deller
2016-11-13 18:56 ` Jeff Law
2016-11-13 19:48 ` Helge Deller
2016-11-14 8:21 ` Jeff Law [this message]
2016-11-14 15:11 ` John David Anglin
2016-11-14 16:24 ` Helge Deller
2016-11-14 17:02 ` John David Anglin
2016-11-14 17:02 ` Jeff Law
2016-11-14 17:23 ` Carlos O'Donell
2016-11-15 18:30 ` Helge Deller
2016-11-16 0:04 ` John David Anglin
2016-11-17 20:19 ` Carlos O'Donell
2016-11-14 13:32 ` Carlos O'Donell
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=06f2cef7-6946-911e-53d8-375637d54096@redhat.com \
--to=law@redhat.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.