This is the mail archive of the
mailing list for the GCC project.
Re: On inlining in C++
- From: Nick Ing-Simmons <nick dot ing-simmons at elixent dot com>
- To: dewar at gnat dot com
- Cc: gcc at gcc dot gnu dot org, aph at redhat dot com
- Date: Tue, 26 Aug 2003 11:41:05 +0100
- Subject: Re: On inlining in C++
- References: <20030804164452.CF402F2D7E@nile.gnat.com>
- Reply-to: Nick Ing-Simmons <nick dot ing-simmons at elixent dot com>
Robert Dewar <firstname.lastname@example.org> writes:
>> Perhaps there is, but the Principle of Least Surprise favours a
>> fairly literal interpretation of "inline".
>I don't agree, a huge blow up in size, resulting in slower execution because
>of icache overload, can also qualify as a surprise.
>Indeed we find that customers are quite often surprised to find that -O3
>is slower than -O2 (as well as generating lots of code).
And of course cache size depends on which hardware is in use,
so what is right for a consumer-oid Celeron is not right for a