This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: std::pow implementation
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Richard dot Earnshaw at arm dot com
- Cc: Karel Gardas <kgardas at objectsecurity dot com>, Alexandre Oliva <aoliva at redhat dot com>, Richard Guenther <rguenth at tat dot physik dot uni-tuebingen dot de>, gcc at gcc dot gnu dot org
- Date: 30 Jul 2003 15:30:08 +0200
- Subject: Re: std::pow implementation
- Organization: Integrable Solutions
- References: <200307301321.h6UDLvK19387@pc960.cambridge.arm.com>
Richard Earnshaw <rearnsha@arm.com> writes:
[...]
| Now, assume that the amount of code in the a!=1 case is reduced. At what
| point does it become beneficial to always inline? Can the programmer
| tell?
He can profile.
| Should he write the code in a separate function, or should he leave
| it to the compiler to decide? What happens if the code is ported to
| another machine with twice as many registers?
Let's not have the compiler speculate about the future plateform the
programmer will run his program on -- it has no clue.
| With Gaby's suggested interpretation, the compiler has *no* choice; it
| must obey the inlining constraint because the programmer always knows
| better... Even when prepared to admit that he doesn't.
That assertion is wrong.
-- Gaby