This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [hurd,commited] hurd: Avoid more libc.so local PLTs

From: Samuel Thibault <samuel dot thibault at ens-lyon dot org>
To: "H.J. Lu" <hjl dot tools at gmail dot com>
Cc: Andreas Schwab <schwab at suse dot de>, GNU C Library <libc-alpha at sourceware dot org>
Date: Tue, 3 Apr 2018 23:07:55 +0200
Subject: Re: [hurd,commited] hurd: Avoid more libc.so local PLTs
References: <20180403003817.21337-1-samuel.thibault@ens-lyon.org> <mvmo9j07lsi.fsf@suse.de> <20180403082029.g3bfw4upbti67wwz@var.youpi.perso.aquilenet.fr> <CAMe9rOoAeQbv6b-1hSTQ9b-EgiC5ErHO3UkS-aZFCFYLn7_xOQ@mail.gmail.com>

Hello,

H.J. Lu, on mar. 03 avril 2018 12:26:33 -0700, wrote:
> __libc_longjmp and __libc_siglongjmp are private external functions provided for
> libpthread.  They should never be called inside libc.

I'm sorry for asking, but are these conventions documented somewhere?
These look like magic to me otherwise: why shouldn't they ever be called
from libc?

Samuel

Follow-Ups:
- Re: [hurd,commited] hurd: Avoid more libc.so local PLTs
  - From: H.J. Lu

References:
- [hurd,commited] hurd: Avoid more libc.so local PLTs
  - From: Samuel Thibault
- Re: [hurd,commited] hurd: Avoid more libc.so local PLTs
  - From: Andreas Schwab
- Re: [hurd,commited] hurd: Avoid more libc.so local PLTs
  - From: Samuel Thibault
- Re: [hurd,commited] hurd: Avoid more libc.so local PLTs
  - From: H.J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]