search for: 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Displaying 2 results from an estimated 2 matches for "0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx".

2015 Sep 08
2
UB and known bits
...own bits need to follow to avoid unsoundness? I remember Nuno and/or David Majnemer saying something about this but I don't have it handy. John %0:i32 = var %1:i32 = lshr %0, 1:i32 %2:i32 = addnw 1:i32, %1 infer %2 known from Souper: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx known from compiler: 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx llvm is stronger %0:i32 = var (000000000000000xxxxxxxxxxxxxxxxx) %1:i32 = and 65535:i32, %0 %2:i16 = var %3:i32 = zext %2 %4:i32 = mulnw %1, %3 infer %4 known from Souper: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx known from compiler: 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx llvm is stronger
2015 Sep 01
3
anyone want to help tune up computeKnownBits()?
...0000000000000000000000000000000000000000000000000000000xx -------------------------------------------------------------------- mul nsw nuw 3, %0 is poison if the MSB is set, so: %0:i32 = var %1:i32 = mulnw 3:i32, %0 infer %1 known from LLVM: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx known from Souper: 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -------------------------------------------------------------------- do we want to follow phis a bit more aggressively? %0 = block 2 %1 = block 2 %2:i64 = phi %1, 0:i64, 1:i64 %3:i64 = phi %0, 1:i64, %2 infer %3 known from LLVM: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx...