On 15 February 2016 at 20:29, Richard Henderson <r...@twiddle.net> wrote: > On 02/16/2016 12:04 AM, Peter Maydell wrote: >> I'm generally reluctant to suggest compiler bugs, but this does >> look rather like a compiler bug... > > > There are at least 5 such bugs open against gcc at the moment. > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56456 > > I couldn't reproduce this quickly with a freshly built gcc 4.8 branch on > i686-linux. Could you please file a gcc bug with your preprocessed source? > There's a chance it isn't a duplicate, but...
Is it worth filing a bug that only repros on a non-upstream gcc? > In the meantime... hmm. I don't suppose removing the inline helps? > Probably not, since there's only one caller... Otherwise I guess we should > go with your "rd & ~1" workaround. We should give it a try with Eric's "stop overriding 'inline' to mean 'always inline', but as you say with only one caller it's probably going to go ahead and inline it anyway. thanks -- PMM
