Metadata in LLVM back-end

Hi all,

Currently metadata (other than debug info) can be attached to IR instructions but disappears during DAG selection.

My question is why we do not keep the metadata during code lowering and then attach to MachineInstr, just as for IR instructions? Is there any technical challenge, or is it only because nobody wants to do so?

Thanks for your help,

Best,

I meet same question with you, and I finnally choose using instrinsic to tag the instruction

ATT00003.txt (158 Bytes)

Son Tuan VU via llvm-dev <llvm-dev@lists.llvm.org> writes:

Currently metadata (other than debug info) can be attached to IR
instructions but disappears during DAG selection.

My question is why we do not keep the metadata during code lowering and
then attach to MachineInstr, just as for IR instructions? Is there any
technical challenge, or is it only because nobody wants to do so?

I have wanted codegen metadata for a very long time so I'm interested to
hear the history behind this choice, and more importantly, whether
adding such capability would be generally acceptable to the community.

                -David

The first questions need to be “what does it mean?”, “how does it work?”, and “what is it useful for?”. It is hard to evaluate a proposal without that.

Metadata isn’t free - it must be maintained or invalidated for it to be useful. The details on that dramatically shape whether it can be used for any given purpose.

-Chris