From: "Andrew Crabtree" <andrewc AT rosemail DOT rose DOT hp DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Speed Test - TC vs. DJGPP
Date: Fri, 6 Mar 1998 16:18:13 -0800
Organization: Hewlett Packard
Lines: 26
Message-ID: <6dq3o6$qu5$1@rosenews.rose.hp.com>
References: <01bd492f$47fb8b40$929175c2 AT ctx> <34FFF92A DOT 3ECF AT cam DOT org> <01bd4945$71bb18e0$8c9175c2 AT ctx>
NNTP-Posting-Host: ros51675cra.rose.hp.com
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk



>Maybe someone can work it out from the assembler dump below.
OK.

> .def _clock_t; .scl 13; .type 04; .endef

This is SDB debugging info.  You typically don't want to request this when
you are trying to
understand assembly dumps.  Also, SDB debugging info and optimizations don't
work too well together.
I'd suggest using STABS debugging info instead (-gstabs instead of -g), or
no debugging at all.

> call ___bb_init_func

Here is your problem.  You have apparently requested that gcc emit basic
block profiling data (-ftest-coverage -fprofile-arcs).  Just get rid of
those options.  Compile with gcc -O3 -Wall and nothing else and see what it
does for you.

HTH

Andy