Re: __syscall_error (was Re: [PATCH v4 13/15] ARC: Build Infrastructure)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 4/1/20 12:58 AM, Andreas Schwab wrote:
> On Apr 01 2020, Vineet Gupta via Libc-alpha wrote:
>> Looking as RISCV code, they opencode __syscall_error for !IS_IN (libc) which I was
>> hoping to avoid.
> But that is the right way to do it.  The syscall error handler must be
> local to the library, it cannot afford to go through the PLT to call a
> function in a different library here.

Still, It needs to fetch (and runtime prepare) the GOT entry anyways.

The real point however is having the call avoids having to know/write asm code
with the errno codegen ABI for TLS model etc

Well its no big deal either way, not these days anyways (Given the ARC embedded
background, I've histrionically been more sensitive to code size, but that
boundary seems to be getting hazy/moot-point anyways...)
linux-snps-arc mailing list

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux