On 11/7/19 7:20 AM, Jan Beulich wrote: > On 24.10.2019 15:31, Jan Beulich wrote: >> The .file assembler directives generated by the compiler do not include >> any path components (gcc) or just the ones specified on the command line >> (clang, at least version 5), and hence multiple identically named source >> files (in different directories) may produce identically named static >> symbols (in their kallsyms representation). The binary diffing algorithm >> used by xen-livepatch, however, depends on having unique symbols. >> >> Provide a Kconfig option to control the (build) behavior, and if enabled >> use objcopy to prepend the (relative to the xen/ subdirectory) path to >> the compiler invoked STT_FILE symbols.
This is a good explanation, and I think the changes make sense. But unfortunately... >> Conditionalize explicit .file directive insertion in C files where it >> exists just to disambiguate names in a less generic manner; note that >> at the same time the redundant emission of STT_FILE symbols gets >> suppressed for clang. Assembler files as well as multiply compiled C >> ones using __OBJECT_FILE__ are left alone for the time being. ...I don't follow this at all. What does the .file directive do in those places, and why is it an issue? And why do we always disable it in clang? -George _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
