Lines Matching refs:OrigIns
47 /// MemorySanitizer can track origins (allocation points) of all uninitialized
48 /// values. This behavior is controlled with a flag (msan-track-origins) and is
51 /// Origins are 4-byte values created and interpreted by the runtime library.
53 /// of application memory. Propagation of origins is basically a bunch of
60 /// MemorySanitizer reports can show unrelated origins, but this is unlikely in
63 /// Origins are meaningless for fully initialized values, so MemorySanitizer
133 /// \brief Track origins of uninitialized values.
137 static cl::opt<int> ClTrackOrigins("msan-track-origins",
138 cl::desc("Track origins (allocation sites) of poisoned memory"),
221 /// \brief Track origins (allocation points) of uninitialized values.
522 Instruction *OrigIns;
524 : Shadow(S), Origin(O), OrigIns(I) { }
612 void materializeOneCheck(Instruction *OrigIns, Value *Shadow, Value *Origin,
614 IRBuilder<> IRB(OrigIns);
634 Cmp, OrigIns,
650 Instruction *OrigIns = ShadowData.OrigIns;
653 materializeOneCheck(OrigIns, Shadow, Origin, InstrumentWithCalls);
1009 void insertShadowCheck(Value *Shadow, Value *Origin, Instruction *OrigIns) {
1018 ShadowOriginAndInsertPoint(Shadow, Origin, OrigIns));
1025 void insertShadowCheck(Value *Val, Instruction *OrigIns) {
1030 insertShadowCheck(Shadow, Origin, OrigIns);
2480 // Origins are always i32, so any vector conditions must be flattened.
2481 // FIXME: consider tracking vector origins for app vectors?
