[PATCH] D14346: Reduce size of MCRelaxableFragment

[Akira Hatanaka via llvm-commits]

ahatanak added a comment.

Currently, MCTargetMachine doesn't seem to have a cache for MCSubtargetInfo (based on what I saw in the patches under review), but I think we can move MCSubtargetAllocator to MCTargetMachine as long as there is a way for target parsers to access MCTargetMachine. What is the advantage of keeping the cache in MCTargetMachine over keeping it in MCContext? It seems like you'll still be creating a new MCSubtargetInfo every time the feature bits are toggled, is that right?


http://reviews.llvm.org/D14346