public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: davidm@hpl.hp.com, libc-hacker@sources.redhat.com,
	davidm@napali.hpl.hp.com
Subject: Re: fix ia64 longjmp() to work from alternate signal-stack
Date: Tue, 31 Aug 2004 16:14:00 -0000	[thread overview]
Message-ID: <16692.41948.53308.392397@napali.hpl.hp.com> (raw)
In-Reply-To: <413499B2.2030900@redhat.com>

>>>>> On Tue, 31 Aug 2004 08:30:58 -0700, Ulrich Drepper <drepper@redhat.com> said:

  Uli> David Mosberger wrote:
  >> Were you able to get clarification on this issue already?

  Uli> Getting a formal answer will take a while.  One reply I got indicated
  Uli> that indeed the altstack is not switched.  So, the public siglongjmp
  Uli> interface need not handle this, just the exception handling stuff.  If
  Uli> it turns out that we want the siglongjmp code to handle this as well
  Uli> some day, we still can enable it.  For now, changing your patch to just
  Uli> implement the cancellation appropriately should go in.

So you want me to create an ia64-specific version of __libc_longjmp()
which will be sigaltstack-safe while everything else goes to
the old longjmp implementation, right?

The only callers of __libc_longjmp() I found are:

./linuxthreads/sysdeps/pthread/ptlongjmp.c:  __libc_longjmp (env, val);
./nptl/sysdeps/pthread/pt-longjmp.c:  __libc_longjmp (env, val);
./nptl/unwind.c:    __libc_longjmp ((struct __jmp_buf_tag *) buf->cancel_jmp_buf, 1);
./nptl/unwind.c:  __libc_longjmp ((struct __jmp_buf_tag *) ibuf->cancel_jmp_buf, 1);

so I think this would have the desired effect.

	--david

  reply	other threads:[~2004-08-31 16:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 16:39 David Mosberger
2004-08-26  9:24 ` Ulrich Drepper
2004-08-26  9:37   ` David Mosberger
2004-08-31 15:10   ` David Mosberger
2004-08-31 15:31     ` Ulrich Drepper
2004-08-31 16:14       ` David Mosberger [this message]
2004-08-31 16:20         ` Ulrich Drepper
2004-08-31 16:20         ` Jakub Jelinek
2004-09-01  8:52           ` David Mosberger
2004-09-02 22:50             ` Ulrich Drepper
2004-09-07 17:36               ` David Mosberger
2004-09-13 17:36                 ` David Mosberger
2004-09-13 18:39                   ` Ulrich Drepper
2004-09-14 17:01                     ` David Mosberger

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=16692.41948.53308.392397@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=davidm@hpl.hp.com \
    --cc=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).