* Tony Lindgren <tony@xxxxxxxxxxx> [120205 08:58]: > * Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [120205 04:28]: > > On Sat, Feb 04, 2012 at 05:25:57PM -0800, Tony Lindgren wrote: > > > * Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [120204 12:03]: > > > > > > > > Another problem (some build errors for OMAP3) do seem to be solved, but > > > > not the section mismatch warnings. They're easy to verify before code > > > > gets pushed anywhere upstream, especially if you're doing one giant OMAP > > > > build - just enable CONFIG_DEBUG_SECTION_MISMATCH in your build > > > > configuration. Refuse patches which introduce section mismatches - at > > > > least without an explanation backing up why they do. > > > > > > > > My OMAP3 and OMAP4 configurations spit out these - I've not even tried > > > > my OMAP2 configuration yet: > > > > > > Weird. The warnings you're seeing all seem valid to me, but I'm not seeing > > > any the section warnings with the following compilers I have: > > > > > > gcc version 4.3.5 (Debian 4.3.5-4) > > > gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) > > > gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70) > > > > > > I see _different_ warnings if I compile with an older gcc: > > > gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51) > > > > > > Any ideas why that would be? > > > > Different inlining behaviour maybe? I'm using stock gcc 4.3.5 here. > > Hmm I'd assume the Emdebian gcc 4.3.5-4 would be very close to the > stock gcc, need to investigate. FYI, I'm now seeing the same warning as Igor posted with omap2plus_defconfig using the same compiler as Igor: gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) Still no other warnings though. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
