This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] powerpc: restore TOC when static longjmp to shared object
- From: Alexander Monakov <amonakov at ispras dot ru>
- To: Rogerio Alves <rcardoso at linux dot vnet dot ibm dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Wed, 23 May 2018 12:26:29 +0300 (MSK)
- Subject: Re: [RFC] powerpc: restore TOC when static longjmp to shared object
- References: <f88767a0-1a38-564d-7bd8-0b5db5bc04df@linux.vnet.ibm.com> <4c67a306-d447-1158-1b92-22ed1cfcfa0a@linux.vnet.ibm.com>
On Tue, 22 May 2018, Rogerio Alves wrote:
> I've attached patch v2 to this email with the fixes suggested by Adhemerval.
Why was it necessary to change the prototype of lbar(), and does the testcase
still demonstrate the issue with that change (does it fail without the patch)?
Note that as soon as gcc is capable of optimizing out the alloca-memset code
in the testcase, it will no longer serve the purpose (maybe it's already
capable, when preparing the testcase I only checked -O0 IIRC). Surely there
are more direct and robust ways of checking that TOC is correctly restored?
Alexander