[PATCH] D21374: [RFC] Generate long nop instructions depending on function-specific subtarget info

Eric Christopher via llvm-commits llvm-commits at lists.llvm.org
Mon Jul 4 10:19:57 PDT 2016

No, that doesn't sound like a good idea. There should be done way of
representing this in assembly.

On Mon, Jul 4, 2016, 6:57 AM Andrey Turetskiy <andrey.turetskiy at gmail.com>

> aturetsk added a comment.
> Can we use llvm.ident metadata which is stored and loaded from an assembly
> file to keep function-specific subtarget information across assembly?
> For example we could store
> "llvm/multiversioning/symbol_name/cpu_name/feature_bits_hex" string in
> ident metadata for functions which subtarget info differs from module's
> info in AsmPrinter::FinalizeMachineFunction.
> http://reviews.llvm.org/D21374
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20160704/c80677e9/attachment.html>

More information about the llvm-commits mailing list