From owner-freebsd-bugs@FreeBSD.ORG Tue Sep 14 09:40:04 2010 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F7CF106564A for ; Tue, 14 Sep 2010 09:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3EBE68FC14 for ; Tue, 14 Sep 2010 09:40:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o8E9e3a0040849 for ; Tue, 14 Sep 2010 09:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o8E9e3dH040847; Tue, 14 Sep 2010 09:40:03 GMT (envelope-from gnats) Date: Tue, 14 Sep 2010 09:40:03 GMT Message-Id: <201009140940.o8E9e3dH040847@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Tijl Coosemans Cc: Subject: Re: kern/131597: [kernel] c++ exceptions very slow on FreeBSD 7.1/amd64 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tijl Coosemans List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2010 09:40:04 -0000 The following reply was made to PR kern/131597; it has been noted by GNATS. From: Tijl Coosemans To: jhb@freebsd.org Cc: bug-followup@freebsd.org, guillaume@morinfr.org, kan@freebsd.org, davidxu@freebsd.org, kostikbel@gmail.com Subject: Re: kern/131597: [kernel] c++ exceptions very slow on FreeBSD 7.1/amd64 Date: Tue, 14 Sep 2010 11:35:48 +0200 On Thu, Jul 08, 2010 at 11:29:50AM -0400, John Baldwin wrote: > ...longjmp(3) isn't safe in a signal context... POSIX says it's supposed to be safe: "As it bypasses the usual function call and return mechanisms, longjmp() shall execute correctly in contexts of interrupts, signals, and any of their associated functions. However, if longjmp() is invoked from a nested signal handler (that is, from a function invoked as a result of a signal raised during the handling of another signal), the behavior is undefined."