Date: Sat, 28 Jun 2008 22:23:23 -0400 From: David Schultz <das@FreeBSD.ORG> To: Bruce Evans <brde@optusnet.com.au> Cc: cvs-src@FreeBSD.ORG, src-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libc/i386/gen _setjmp.S setjmp.S Message-ID: <20080629022323.GA39584@zim.MIT.EDU> In-Reply-To: <20080629110524.W92369@delplex.bde.org> References: <200806281758.m5SHwIl2083857@repoman.freebsd.org> <20080628180230.GA37313@zim.MIT.EDU> <20080629110524.W92369@delplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080629022323.GA39584>