delorie.com/archives/browse.cgi | search |
From: | buers AT gmx DOT de (Dieter Buerssner) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: inefficiency of GCC output code & -O problem |
Date: | 18 Apr 2000 06:31:09 GMT |
Lines: | 13 |
Message-ID: | <8dh0tn.3vvqu6v.0@buerssner-17104.user.cis.dfn.de> |
References: | <Pine DOT LNX DOT 4 DOT 10 DOT 10004180455310 DOT 1540-100000 AT darkstar DOT grendel DOT net> |
NNTP-Posting-Host: | pec-104-133.tnt5.s2.uunet.de (149.225.104.133) |
Mime-Version: | 1.0 |
X-Trace: | fu-berlin.de 956039469 8119095 149.225.104.133 (16 [17104]) |
X-Posting-Agent: | Hamster/1.3.13.0 |
User-Agent: | Xnews/03.02.04 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Kalum Somaratna aka Grendel wrote: >It once again proved that a good optimising compiler can do a excellent >job...also the wisdom of running a profiler and seing which routines take >up most time... I can say one thing in the defense of Alexei. I don't know, whether he used the profiler, or not. But there is profiling code in his sources. I did a very quick profile of his code. IHMO, he correctly identified the bottlenecks. -- Regards, Dieter
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |