delorie.com/archives/browse.cgi | search |
Date: | Tue, 18 Mar 2003 08:15:23 +0200 |
From: | "Eli Zaretskii" <eliz AT elta DOT co DOT il> |
Sender: | halo1 AT zahav DOT net DOT il |
To: | alexvn AT bigfoot DOT com |
Message-Id: | <4331-Tue18Mar2003081523+0200-eliz@elta.co.il> |
X-Mailer: | emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 |
CC: | djgpp AT delorie DOT com |
In-reply-to: | <b568o6$258tun$1@ID-79865.news.dfncis.de> (alexvn@bigfoot.com) |
Subject: | Re: gcc -O3 & gprof |
References: | <b54db9$252aq3$1 AT ID-79865 DOT news DOT dfncis DOT de> <Oejda.183$Zf2 DOT 42 AT read3 DOT inet DOT fi> <b568o6$258tun$1 AT ID-79865 DOT news DOT dfncis DOT de> |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> From: "Alex Vinokur" <alexvn AT bigfoot DOT com> > Newsgroups: comp.os.msdos.djgpp,gnu.gcc.help,gnu.utils.help > Date: Tue, 18 Mar 2003 06:52:29 +0200 > > > > The optimisation -O3 inlines simple functions (like yours here). There are > > no calls to trace. > [snip] > > How can we see that ? By using the -S switch to GCC and looking at the produced assembly. "objdump --disassemble a3.exe" could also help.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |