On Thu, Jun 18, 2015 at 9:33 AM, Vineet Gupta <vineet.gup...@synopsys.com> wrote: > On Thursday 18 June 2015 12:40 PM, Geert Uytterhoeven wrote: >> On Thu, Jun 18, 2015 at 8:47 AM, Vineet Gupta >> <vineet.gup...@synopsys.com> wrote: >>> > commit a1c48bb160f8368 "Makefile: Fix unrecognized cross-compiler command >>> > line >>> > options" moved ARCH specific cc option handling before common -Os/O2 >>> > setup. >>> > >>> > For ARC this had a subtle effect that we can no longer over-ride generic >>> > -O2 with >>> > -O3, hence a performance regression observed going from 3.13 to 3.18 (the >>> > above >>> > commit went into 3.16) >>> > >>> > I want to understand how to properly fix this. Moving the include of arch >>> > makefile >>> > will bring back the old issue. I can introduce another option to set >>> > default optim >>> > level, but only arc/m32r care about it anyways. >> Can we include $(srctree)/arch/$(SRCARCH)/Makefile twice? > > Something like this would be ideal, but does that not bring back your > warnings ?
I don't think so. The warnings were caused by using the host compiler instead of the cross compiler while checking for the support of some compiler options. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/