>> At one point were discussed eliminating >> TII::isTriviallyReMaterializable. The argument is that target >> implementations shouldn't have to know about algorithms, they should >> just describe properties of the target, and the algorithm should >> figure out if it can make the xform from that info. > > What do you mean? The targets don't know about the remat algorithm. > It's just the spiller making use of a some property of the > instructions.
The comment above isTriviallyReMaterializable says: /// isTriviallyReMaterializable - Return true if the instruction is trivially /// rematerializable, meaning it has no side effects and requires no operands /// that aren't always available. Why not just expose the properties "has no side effects" and "requires no operands that are not always available"? -Chris _______________________________________________ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
