From: "Alex Vinokur" Newsgroups: comp.os.msdos.djgpp,comp.lang.c++ Subject: Re: Optimization and operator&& Date: Wed, 5 Jun 2002 14:35:07 +0200 Organization: Scopus Network Technologies Lines: 23 Message-ID: References: <3CFCB642 DOT 252CFFF7 AT bigfoot DOT com> <3CFCDBF9 DOT CCDA33 AT bigfoot DOT com> NNTP-Posting-Host: gateway.scopus.net (62.90.123.5) X-Trace: fu-berlin.de 1023276794 59533 62.90.123.5 (16 [79865]) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Heinz Ozwirk" wrote in message news:adin9l$s7q$00$1 AT news DOT t-online DOT com... > "Alex Vinokur" wrote in message [snip] > But that doesn't answer your question, and I cannot do so. Common sense > suggests that optimized code should be faster than plain code and if a > compiler slows down a program when optimizing might be a hint that the > compiler does something wrong. Or the uclock() function is not the proper > tool for timing code. > Similar results have been received when using the getrusage() function http://www.mcsr.olemiss.edu/cgi-bin/man-cgi?getrusage+3 and 'struct timeval ru_stime' in 'struct rusage'. > Regards > Heinz > >