From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: things to do for arch maintainers
Date: Sun, 18 Dec 2005 19:11:00 -0000 [thread overview]
Message-ID: <43A5B402.10007@redhat.com> (raw)
1. on the setjmp code, make sure that for the code ending up inside
ld.so we don't call __sigjmp_save (see the x86, x86-64, ppc code)
2. add pointer_guard to tcbhead_t in <tls.h>
3. define THREAD_SET_POINTER_GUARD and THREAD_COPY_POINTER_GUARD in <tls.h>
4. in <sysdep.h>, define PTR_MANGLE and PTR_DEMANGLE. The ld.so code
must use the global variable __pointer_chk_guard_local. The libc code
must use the tcbhead_t value. C and asm versions are needed. See the
x86-64 version
All needs to be done for archs other than x86 and x86-64 (although 1 is
done for ppc).
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA â–
next reply other threads:[~2005-12-18 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 19:11 Ulrich Drepper [this message]
2005-12-19 22:12 ` Jakub Jelinek
2005-12-20 6:55 ` Ulrich Drepper
2005-12-20 9:09 ` Kaz Kojima
2005-12-20 15:32 ` Ulrich Drepper
2005-12-21 0:57 ` Kaz Kojima
2005-12-20 21:08 ` Steven Munroe
2005-12-20 21:13 ` Jakub Jelinek
2005-12-20 23:34 ` Steven Munroe
2005-12-20 23:58 ` Roland McGrath
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=43A5B402.10007@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.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).