public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: davidm@hpl.hp.com
Cc: libc-hacker@sources.redhat.com
Subject: Re: fix ia64 longjmp() to work from alternate signal-stack
Date: Mon, 13 Sep 2004 18:39:00 -0000	[thread overview]
Message-ID: <4145E966.9090609@redhat.com> (raw)
In-Reply-To: <16709.55979.414777.757138@napali.hpl.hp.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've applied the patch after minor changes.  There is no need to require
the sigaltstack function being exported from libc.so.  It's a simple
syscall, just inline it.  Plus, even if the function would have needed
to be exported this must have happened only for ia64 and no other arch.

The result seems to work for me but then, I never saw the problem this
is supposed to fix in the first place.

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFBRell2ijCOnn/RHQRAvAfAKC+gd+9aAaQJj6lPNSHGXUnvo7eDwCffxEV
JM0EVyUYUDBX235Ru3eLP4E=
=eb5k
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-09-13 18:39 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
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 [this message]
2004-09-14 17:01                     ` David Mosberger
2004-08-31 16:20         ` Ulrich Drepper

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=4145E966.9090609@redhat.com \
    --to=drepper@redhat.com \
    --cc=davidm@hpl.hp.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).