From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17931 invoked by alias); 31 Aug 2004 16:20:48 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 17911 invoked from network); 31 Aug 2004 16:20:48 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 31 Aug 2004 16:20:48 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i7VGKgS2015431 for ; Tue, 31 Aug 2004 12:20:43 -0400 Received: from lacrosse.corp.redhat.com (lacrosse.corp.redhat.com [172.16.52.154]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i7VGKg320293; Tue, 31 Aug 2004 12:20:42 -0400 Received: from [10.0.1.84] (drepper.cipe.redhat.com [10.0.1.84]) by lacrosse.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i7VGKYr02304; Tue, 31 Aug 2004 12:20:36 -0400 Message-ID: <4134A53C.3070300@redhat.com> Date: Tue, 31 Aug 2004 16:20:00 -0000 From: Ulrich Drepper Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040830 MIME-Version: 1.0 To: davidm@hpl.hp.com CC: libc-hacker@sources.redhat.com, davidm@napali.hpl.hp.com Subject: Re: fix ia64 longjmp() to work from alternate signal-stack References: <16684.49335.802840.212013@napali.hpl.hp.com> <412DAC31.1050404@redhat.com> <16692.38122.52348.850833@napali.hpl.hp.com> <413499B2.2030900@redhat.com> <16692.41948.53308.392397@napali.hpl.hp.com> In-Reply-To: <16692.41948.53308.392397@napali.hpl.hp.com> X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2004-08/txt/msg00090.txt.bz2 David Mosberger wrote: > 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? Basically, yes. Not sure we should keep the name, though. And even for other archs, we might have to reset the stack. Even though the current code might everywhere in the moment does not mean it is correct. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖