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
Subject: Re: fix ia64 longjmp() to work from alternate signal-stack
Date: Tue, 14 Sep 2004 17:01:00 -0000	[thread overview]
Message-ID: <16711.9210.702107.62167@napali.hpl.hp.com> (raw)
In-Reply-To: <4145E966.9090609@redhat.com>

>>>>> On Mon, 13 Sep 2004 11:39:34 -0700, Ulrich Drepper <drepper@redhat.com> said:

  Uli> I've applied the patch after minor changes.  There is no need
  Uli> to require the sigaltstack function being exported from
  Uli> libc.so.  It's a simple syscall, just inline it.

OK, that's certainly fine by me.

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

I re-checked and the test-suite (in particular tst-cancel20) still
passes, so everything seems fine.  (As a reminder, you don't see the
problem with a GCC that's using the built-in unwinder since the
built-in unwinder maskes the problem due to some excessive copying;
the problem only shows when using a GCC that has libunwind enabled.)

Thanks,

	--david

      reply	other threads:[~2004-09-14 17:01 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         ` 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 [this message]

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=16711.9210.702107.62167@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).