This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: New badness metric for inliner
From: David Miller <davem@davemloft.net>
Date: Tue, 06 Nov 2012 14:28:19 -0500 (EST)
> Or perhaps we can get away with only using gcov_t for info->time, I'll
> give that a try.
That gets thing further, but if the edge times add up to such large
values it seems we have lots of other potential problems.
With info->times converted to gcov_type, the next assertion I hit is:
gcc_assert (cached_badness == current_badness);
in inline_small_functions().
Both badness values are negative.
(gdb) p cached_badness
$1 = -91472
(gdb) p current_badness
$2 = -11434
This is starting to look like a very deep rabbit hole, and I'm really
surprised that you hit none of these problems. Especially since even
x86-64 is getting fortran testsuite failure regressions due to these
changes.