Date: Wed, 13 Mar 2002 12:15:34 -0800 From: Ed Hall <edhall@weirdnoise.com> To: Martin Blapp <mb@imp.ch> Cc: Kris Kennaway <kris@obsecurity.org>, Jan Stocker <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: <200203132015.g2DKFYv17886@screech.weirdnoise.com> In-Reply-To: Message from Martin Blapp <mb@imp.ch> of "Wed, 13 Mar 2002 14:08:55 %2B0100." <20020313140429.B2573-100000@levais.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
This problem should exist in -current since I think FreeBSD finally drops
setjmp/longjmp stack unwinds and goes to dwarf 2 unwinds, which do work
(and which are used by the GCC 2.95 port, which also works but which
isn't compatible with /usr/lib/libstdc++.{a,so}).
This issue is why Yahoo! has to use its own build of GCC, and I doubt
we're the only ones...
-Ed
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?200203132015.g2DKFYv17886>