From owner-cvs-all@FreeBSD.ORG Sun Jun 29 04:13:39 2008 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 059221065701; Sun, 29 Jun 2008 04:13:39 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail08.syd.optusnet.com.au (mail08.syd.optusnet.com.au [211.29.132.189]) by mx1.freebsd.org (Postfix) with ESMTP id 7D6D28FC12; Sun, 29 Jun 2008 04:13:38 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from c220-239-252-11.carlnfd3.nsw.optusnet.com.au (c220-239-252-11.carlnfd3.nsw.optusnet.com.au [220.239.252.11]) by mail08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5T4DYQc029768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Jun 2008 14:13:36 +1000 Date: Sun, 29 Jun 2008 14:13:34 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: David Schultz In-Reply-To: <20080629022323.GA39584@zim.MIT.EDU> Message-ID: <20080629140956.G92769@delplex.bde.org> References: <200806281758.m5SHwIl2083857@repoman.freebsd.org> <20080628180230.GA37313@zim.MIT.EDU> <20080629110524.W92369@delplex.bde.org> <20080629022323.GA39584@zim.MIT.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, Bruce Evans Subject: Re: cvs commit: src/lib/libc/i386/gen _setjmp.S setjmp.S X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 04:13:39 -0000 On Sat, 28 Jun 2008, David Schultz wrote: > On Sun, Jun 29, 2008, Bruce Evans wrote: >> On Sat, 28 Jun 2008, David Schultz wrote: >>> Don't clobber the FPU exception flags in longjmp. C99 requires them >>> to remain unchanged. >>> >>> ...but got cut off somehow. >> >> This is wrong. It breaks longjmp() from all COMPAT_[3-4] signal >> handlers (not just ones for SIGFPE). I don't like the corresponding >> change for amd64 either, and only approved it since amd64 doesn't >> support COMPAT_[3-4] signal handlers. > > How is it possible for an application linked against an 8.X libc, > and which is doing anything even remotely close to reasonable, > to get COMPAT_3 or COMPAT_4 signal behavior? Nevermind. I forgot the layering. Bruce