Some more info before you report the bug to the gcc people - looking at
my kernel build logs from the past week, it seems to be a gcc 2.95.x
thing (maybe a 2.96 thing as well). It appears to be fixed in gcc 3.2.1.
I'm in favour of putting up with the incorrect warning produced by older
-- Russell King (firstname.lastname@example.org) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/