cdevadas wrote: The intention here is to bypass NPM for GISel. However, I do agree that this approach is too much for just bypassing the GISel scenario. If a target wishes to enable NPM for its backend by default while the GlobalISel infrastructure has not yet been fully ported to NPM, what should we do now? Does it make sense to introduce a TargetMachine flag (e.g., NewPMForBackend) that allows targets to independently control backend NPM adoption? With this TM field, the target can choose to disable NPM for the GlobalISel path and can enable NPM by default for the SelectionDAG.
https://github.com/llvm/llvm-project/pull/210248 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
