From owner-freebsd-current Thu Mar 14 7:41:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 126B037B400; Thu, 14 Mar 2002 07:41:10 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g2EFf4i36664; Thu, 14 Mar 2002 08:41:05 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g2EFewL49717; Thu, 14 Mar 2002 08:40:58 -0700 (MST) (envelope-from imp@village.org) Date: Thu, 14 Mar 2002 08:40:35 -0700 (MST) Message-Id: <20020314.084035.00348970.imp@village.org> To: tlambert2@mindspring.com 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 From: "M. Warner Losh" In-Reply-To: <3C9048FC.1C9C57B5@mindspring.com> References: <200203132015.g2DKFYv17886@screech.weirdnoise.com> <20020313.234345.88856963.imp@village.org> <3C9048FC.1C9C57B5@mindspring.com> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <3C9048FC.1C9C57B5@mindspring.com> Terry Lambert writes: : "M. Warner Losh" wrote: : > In message: <200203132015.g2DKFYv17886@screech.weirdnoise.com> : > Ed Hall 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... Yes, that works. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message