[PATCH] [inline-asm] Fix scope of assembly macros
Reid Kleckner
rnk at google.com
Wed Dec 3 11:22:55 PST 2014
For LTO, what if we make Clang responsible for using the same asm context, and have it expand macros before creating the IR? We would still have the problem that llc's .s emission would produce different object files than it produces directly. We could have LLVM's LTO infrastructure expand .macro prior to linking, but that could kill lazy linking. We could also change AsmPrinter to undefine any macros introduce with .macro at the end of an asm blob, but still have Clang ask for the expansion.
I don't like any of this. Maybe we should just reject .macro in inline asm.
http://reviews.llvm.org/D6383
More information about the llvm-commits
mailing list