Re: [Valgrind-developers] Inlining failing in Callgrind

[Julian S. <js...@ac...>]

gcc-3.3 seems to be markedly less enthusiastic about inlining than
other versions -- both earlier and later versions.  As Josef says,
later gcc's don't show this problem.  But I think using the INLINE
macro might be a good thing since all those warning messages 
make it harder to see real errors (I aim to have a completely silent
"make --quiet", apart from the printing of the top level directory
names).

J

On Saturday 21 October 2006 16:30, Nicholas Nethercote wrote:
> Josef,
>
> With gcc 3.3.4 I get a lot of 'inlining failed in call to X' messages from
> GCC (see attachment).  Some of them look like they are important for
> Callgrind's speed.  If they are, you might like to look at Memcheck's
> INLINE macro which tries harder than usual to inline functions.
>
> Nick