[libc-dev] [musl] Powerpc Linux 'scv' system call ABI proposal take 2
Florian Weimer via libc-dev
libc-dev at lists.llvm.org
Fri Apr 17 01:34:57 PDT 2020
* Segher Boessenkool:
> On Thu, Apr 16, 2020 at 08:34:42PM -0400, Rich Felker wrote:
>> On Thu, Apr 16, 2020 at 06:02:35PM -0500, Segher Boessenkool wrote:
>> > On Thu, Apr 16, 2020 at 08:12:19PM +0200, Florian Weimer wrote:
>> > > > I think my choice would be just making the inline syscall be a single
>> > > > call insn to an asm source file that out-of-lines the loading of TOC
>> > > > pointer and call through it or branch based on hwcap so that it's not
>> > > > repeated all over the place.
>> > >
>> > > I don't know how problematic control flow out of an inline asm is on
>> > > POWER. But this is basically the -moutline-atomics approach.
>> > Control flow out of inline asm (other than with "asm goto") is not
>> > allowed at all, just like on any other target (and will not work in
>> > practice, either -- just like on any other target). But the suggestion
>> > was to use actual assembler code, not inline asm?
>> Calling it control flow out of inline asm is something of a misnomer.
>> The enclosing state is not discarded or altered; the asm statement
>> exits normally, reaching the next instruction in the enclosing
>> block/function as soon as the call from the asm statement returns,
>> with all register/clobber constraints satisfied.
> Ah. That should always Just Work, then -- our ABIs guarantee you can.
After thinking about it, I agree: GCC will handle spilling of the link
register. Branch-and-link instructions do not clobber the protected
zone, so no stack adjustment is needed (which would be problematic to
reflect in the unwind information).
Of course, the target function has to be written in assembler because
it must not use a regular stack frame.
More information about the libc-dev