Josh Poimboeuf <jpoimboe@xxxxxxxxxx> writes: > > If you're wanting something like -freorder-blocks-and-partition for asm > code, maybe we could implement something analagous to the > likely()/unlikely() macros, to allow the hot and cold portions to be > placed into different sections. (I could then teach asmvalidate how to > validate such code.) > > Would that be useful? Eventually you have to handle dwarf4, because that's the only way to handle the gcc generated code. So your tool just needs to understand the dwarf. It's ok to warn about assembler code that is not correctly annotated, and fix it then. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe live-patching" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
