This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.3 release criteria
- From: dewar at gnat dot com (Robert Dewar)
- To: austern at apple dot com, drow at mvista dot com
- Cc: gcc at gcc dot gnu dot org, hch at infradead dot org, lars dot segerlund at comsys dot se,m dot hayes at elec dot canterbury dot ac dot nz, stuart at apple dot com,tm_gccmail at mail dot kloo dot net
- Date: Tue, 25 Feb 2003 20:14:43 -0500 (EST)
- Subject: Re: GCC 3.3 release criteria
> Yes and no. One section, "an inline function is as fast as a macro",
> implies that a function that's declared inline will always be
> inlined (at least if you're using -O and if the function doesn't use
> constructs that are unsuitable for inlining).
This seems a reasonable expectation for sure (that if you ask for a functoin
to be inlined, and the function doesn't use constructs that are unsuitable
for inlining, and you are using -O, then calls should be inlined, assuming
this will in fact generate faster code, as is the case on most processors.
Note also that inlining helps avoid cache flushing anomolies.