Lines Matching full:lattice

10 // modeled after SCCP, but with a customizable lattice function.
39 /// to specify what the lattice values are and how they handle merges etc.  This
40 /// gives the client the power to compute lattice values from instructions,
41 /// constants, etc.  The current requirement is that lattice values must be
43 /// lattice keys must be able to be used as keys of a mapping data structure.
44 /// Internally, the generic solver currently uses a DenseMap to map lattice keys
45 /// to lattice values.  If the lattice key is a non-standard type, a
80   /// MergeValues - Compute and return the merge of the two specified lattice
81   /// values.  Merging should only move one direction down the lattice to
111 /// Propagation with a programmable lattice function.
115   /// LatticeFunc - This is the object that knows the lattice and how to
139       AbstractLatticeFunction<LatticeKey, LatticeVal> *Lattice)  in SparseSolver()  argument
140       : LatticeFunc(Lattice) {}  in SparseSolver()
164   /// AggressiveUndef is true, then this treats values with unknown lattice
166   /// lattice, not when querying it.
172   /// querying the lattice.
215     OS << "unknown lattice value";  in PrintLatticeVal()
221   OS << "unknown lattice key";  in PrintLatticeKey()
400   // The lattice function may store more information on a PHINode than could be  in visitPHINode()