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: Michael Matz <matz at suse dot de>
- Cc: Steven Bosscher <s dot bosscher at student dot tudelft dot nl>, Richard Guenther <rguenth at tat dot physik dot uni-tuebingen dot de>, <gcc at gcc dot gnu dot org>
- Date: 29 Jul 2003 16:42:57 +0200
- Subject: Re: std::pow implementation
- Organization: Integrable Solutions
- References: <Pine.LNX.4.44.0307291634350.17944-100000@wotan.suse.de>
Michael Matz <matz@suse.de> writes:
| Hi,
|
| On 29 Jul 2003, Gabriel Dos Reis wrote:
|
| > | Well how do you suggest we make the compiler to its job better then?
| >
| > Start with removing the requirement that whether a function should be
| > inlined depends on its context of use.
|
| So it should be inlined independend of the context?
You missed "of use".
| Well, that for sure _is_ nonsense, sorry.
It is nonsense only after you have modified what I said.
A simple function like 'std::string::end() const' should be cost-free.
Providing a controled access to a protected data should be as efficient
as accessing that data directly. Protection is a compile time notion.
-- Gaby