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: Karel Gardas <kgardas at objectsecurity dot com>
- Cc: Richard dot Earnshaw at arm 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 14:54:30 +0200
- Subject: Re: std::pow implementation
- Organization: Integrable Solutions
- References: <Pine.LNX.4.43.0307301442420.24593-100000@thinkpad.c0202001.roe.itnq.net>
Karel Gardas <kgardas@objectsecurity.com> writes:
| On Wed, 30 Jul 2003, Gabriel Dos Reis wrote:
|
| > Firstly, I do not trust you that counting lines is sensical mesure for
| > inlining. Secondly, it is up to the programmer to decide whether he
| > wants the 2000 lines in the middle his class. Whether it is stupid
| > depends on what he is doing and *you* have no cluie to know that.
| >
| > Do trust the programmer.
|
| As a gcc user, I would just like to say, that it would be nice, if there
| is some kind of ``wrong inline'' warning which might teach programmers
| about what compiler thinks about inline - of course compiler should honour
| inline even in the case of wrong usage... The programmer is responsible
| for removing it in this case...
GCC has a switch named -Winline that is supposed to give a warning
about functions it can't inline and the reason why. But, currently it
is not really helpful because of the inlining strategy.
But your suggestion about something like -frank-my-usage-of-inline
might also be helpful also.
-- Gaby