http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57698
--- Comment #6 from Markus Trippelsdorf <markus at trippelsdorf dot de> --- (In reply to Jan Hubicka from comment #3) > Hmm, > the problem here is that we output errors after early inlining always now, > while previously we did > only when some other inlining happened in the function (adding extra early > inlinable function > to the testcase should reproduce the error message on early GCC releases). > We can fix by outputting always inline errors only after real inliner was > run (when optimizing) > but then such testcases won't compile at -O0 that is uncool too. I"m not sure if I understand you correctly, but the test-case compiles just fine at -O0. So outputting the always inline errors only after the real inliner was run should fix the issue. No?
