On Saturday 24 August 2013, Frantisek Hrbata wrote: > If I understand it correctly, this would mean that you will be able to use only > one implementation of gcov format at the time. Meaning you will be able to get > coverage data for module, but not for kernel if it was compiled with different > gcc(gcda format). This is probably ok if you work only on your module, but I'm > not sure this is generally the right approach. In this case I would probably > rather see some support for more gcov formats at the same time(e.g. set of > callback operations per gcov version). Again I'm probably missing something, but > I still cannot see reason why to add such feature. If you want gcov support just > compile your kernel and modules with the same gcc version(gcda format). But if > this is really needed maybe it would be better to consider some parallel support > for more gcov formats based on the gcov_info version. The kernel is always built with exactly one version, including all the modules. I don't see any reason whatsoever to support externally built modules with gcov, in particular when they are not built with the system compiler. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
