Date: Wed, 13 Mar 2002 22:53:48 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: "M. Warner Losh" <imp@village.org> Cc: edhall@weirdnoise.com, mb@imp.ch, kris@obsecurity.org, jstocker@tzi.de, current@FreeBSD.ORG, hackers@FreeBSD.ORG, obrien@FreeBSD.ORG, edhall@screech.weirdnoise.com Subject: Re: gcc -O broken in CURRENT Message-ID: <3C9048FC.1C9C57B5@mindspring.com> References: <mb@imp.ch> <200203132015.g2DKFYv17886@screech.weirdnoise.com> <20020313.234345.88856963.imp@village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"M. Warner Losh" wrote: > In message: <200203132015.g2DKFYv17886@screech.weirdnoise.com> > Ed Hall <edhall@weirdnoise.com> writes: > : 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. > > Hmmmm, C++ exceptions work in -stable with -O and have for at least a > year. At least they are working for us in our environment. What's > busted? Per thread exception stacks? THat's where I'd look... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C9048FC.1C9C57B5>