Lines Matching refs:optimized

262 ``MemoryUse``\ s keep a single operand, which is their defining or optimized
264 Traditionally ``MemorySSA`` optimized ``MemoryUse``\ s at build-time, up to a
266 Specifically, the operand of every ``MemoryUse`` was optimized to point to the
285 The second operand is the optimized access, if there was a previous call on the
291 A walk of the uses for any MemoryDef can find the accesses that were optimized
297   MemoryDef *Def;  // find who's optimized or defining for this MemoryDef
302         // User who is optimized to Def
304         // User who's defining access is Def; optimized to something else or not optimized.
308 When ``MemoryUse``\ s are optimized, for a given store,  you can find all loads
323         // As a user can come up twice, as an optimized access and defining
473 optimized" (it can provide a more acccurate result than if it were recomputed
474 from scratch), or "under optimized" (it could infer more if it were recomputed).
482 updates an optimized access of a store, after a traversal that guarantees the