From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18161 invoked by alias); 24 Mar 2004 17:03:45 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 17867 invoked by uid 48); 24 Mar 2004 17:03:41 -0000 Date: Wed, 24 Mar 2004 17:03:00 -0000 Message-ID: <20040324170341.17864.qmail@sources.redhat.com> From: "bangerth at dealii dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040312233606.14563.paulthomas2@wanadoo.fr> References: <20040312233606.14563.paulthomas2@wanadoo.fr> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug c++/14563] octave built under Cygwin very slow X-Bugzilla-Reason: CC X-SW-Source: 2004-03/txt/msg02931.txt.bz2 List-Id: ------- Additional Comments From bangerth at dealii dot org 2004-03-24 17:03 ------- sjsl exceptions is one way to implement exception handling. On most systems, we have moved to more efficient ways, such as dwarf2 unwinding. However, if you don't use exceptions, trying things out with -fno-exceptions may be an interesting experiment anyway. Regarding the times not adding up: I think this is usual for gprof. In fact, gprof is not a very good tool anyway, but it is the one that is most widely available. There are more accurate ones, which I have never used myself, though, so I can't say anything about them. I think I remember people being quite fond of oprof. It may also be the case that valgrind can produce some sort of information, but I don't know about that exactly. W. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14563