From: Steve Munroe <sjmunroe@us.ibm.com>
To: libc-hacker@sources.redhat.com
Cc: sjmunroe@vnet.ibm.com
Subject: Versioning longjmp etc.
Date: Fri, 17 Oct 2003 20:47:00 -0000 [thread overview]
Message-ID: <OFEA0A540B.27E0BA5C-ON86256DC2.0070BECC-86256DC2.00722D46@us.ibm.com> (raw)
We are looking at integrating Vector Extensions (AKA Altivec or VMX) into
glibc for PPC32/PPC64. This will change the size of __jmp_buf and
sigcontext/ucontext and requires versioning of the corresponding functions
(setjmp/longjmp etc).
I assume this includes the complete function stack, for example
[siglongjmp | longjmp] -> [__libc_siglongjmp | __libc_longjmp] ->
__longjmp.
But looking at linuxthreads/ptlongjmp.c and nptl/pt-longjmp.c I don't
understand why we need the siglongjmp()/longjmp() stubs. They add
path-length without adding any function (at least in the current
implementation).
So could these stubs be eliminated and replaced with aliases? If they are
required where should I move ptlongjmp.c to (sysdeps/pthreads,
sysdeps/generic, ...) so I can override it for powerpc[32 | 64]? Or should
the siglongjmp()/longjmp() stubs be split out of ptlongjmp.c?
next reply other threads:[~2003-10-17 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 20:47 Steve Munroe [this message]
2003-10-17 20:56 ` Ulrich Drepper
2003-10-17 21:12 Steve Munroe
2003-10-17 21:27 ` Ulrich Drepper
2003-10-17 22:27 Steve Munroe
2003-10-24 22:57 Steve Munroe
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=OFEA0A540B.27E0BA5C-ON86256DC2.0070BECC-86256DC2.00722D46@us.ibm.com \
--to=sjmunroe@us.ibm.com \
--cc=libc-hacker@sources.redhat.com \
--cc=sjmunroe@vnet.ibm.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).