Date: Wed, 13 Mar 2002 12:24:22 -0800 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Ed Hall <edhall@weirdnoise.com> Cc: Martin Blapp <mb@imp.ch>, Kris Kennaway <kris@obsecurity.org>, Jan Stocker <jstocker@tzi.de>, current@FreeBSD.ORG, hackers@FreeBSD.ORG, edhall@screech.weirdnoise.com Subject: Re: gcc -O broken in CURRENT Message-ID: <20020313122422.A13044@dragon.nuxi.com> In-Reply-To: <200203132015.g2DKFYv17886@screech.weirdnoise.com>; from edhall@weirdnoise.com on Wed, Mar 13, 2002 at 12:15:34PM -0800 References: <mb@imp.ch> <200203132015.g2DKFYv17886@screech.weirdnoise.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 13, 2002 at 12:15:34PM -0800, Ed Hall wrote: > Exception-handling is broken with -O in -stable, and has been for years. > FreeBSD is one of the few systems that use setjmp/longjmp stack unwinds > to implement exceptions, so when the GCC folks broke that path, it was > never fixed. There are supposedly patches floating around that fix the > problem, but they either didn't work as advertised or the ball got dropped. We are using a set of patches that were part of gcc 2.95.3_test3. Do you have a sample program in which exceptions are still broken on FreeBSD 4.5? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020313122422.A13044>