> I think that's the point. gcc will not get it right. I don't think that's necessary an universal truth. It can be probably fixed. > So we need to do it ourselves in the kernel sources. > We may not like it, but it's the only way to guarantee reproducable > reliable inline / noinline decisions. For most things we don't really need it to be reproducable, the main exception are the inlines in headers. Universal noinline would also be a bad idea because of its costs (4.1% text size increase). Perhaps should make it a CONFIG option for debugging though. -Andi > > /D > > -- > Dirk Hohndel > Intel Open Source Technology Center > -- ak@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
