I still suspect that because the behaviour is different between 4.1 and 4.2, it might be a regression in 4.2,
The kernel code is wrong. It might have accidentally worked with GCC-4.1, but that doesn't mean GCC-4.2 has regressed. Only supported features that stop working are regressions; invalid code that stops working is, well, in the worst case an improvement in diagnostics ;-) Segher - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
