From: Andreas Schwab <schwab@suse.de>
To: Zack Weinberg <zackw@panix.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
"H.J. Lu" <hjl.tools@gmail.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [hurd,commited] hurd: Avoid more libc.so local PLTs
Date: Wed, 04 Apr 2018 07:20:00 -0000 [thread overview]
Message-ID: <mvmo9iz4euy.fsf@suse.de> (raw)
In-Reply-To: <CAKCAbMjCPCHGZzARPnQO8+iBrgoAmNRZ6U4LKU5+PTVH=cVRgQ@mail.gmail.com> (Zack Weinberg's message of "Tue, 3 Apr 2018 18:33:47 -0400")
On Apr 03 2018, Zack Weinberg <zackw@panix.com> wrote:
> Joseph would know better than me, but I _think_ it's still necessary
> to avoid using the application-namespace names. For instance, a
> program that uses fork, but not siglongjmp, might have defined its own
> siglongjmp
I don't think so, since both fork and siglongjmp are part of POSIX (any
version), but neither is part of any narrower standard.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-04-04 7:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 0:38 Samuel Thibault
2018-04-03 8:10 ` Andreas Schwab
2018-04-03 8:20 ` Samuel Thibault
2018-04-03 9:02 ` Stefan Liebler
2018-04-03 19:26 ` H.J. Lu
2018-04-03 20:51 ` H.J. Lu
2018-04-03 21:08 ` Samuel Thibault
2018-04-03 21:16 ` H.J. Lu
2018-04-03 21:24 ` Samuel Thibault
2018-04-03 21:41 ` H.J. Lu
2018-04-03 21:55 ` Samuel Thibault
2018-04-03 22:14 ` H.J. Lu
2018-04-03 22:18 ` Samuel Thibault
2018-04-03 22:21 ` H.J. Lu
2018-04-03 22:30 ` Samuel Thibault
2018-04-03 22:21 ` Zack Weinberg
2018-04-03 22:28 ` Samuel Thibault
2018-04-03 22:33 ` Zack Weinberg
2018-04-04 7:20 ` Andreas Schwab [this message]
2018-04-03 22:39 ` Samuel Thibault
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=mvmo9iz4euy.fsf@suse.de \
--to=schwab@suse.de \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=zackw@panix.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).