Fix a memcheck anomaly observed by Nick: lazy propagation of
undefinedness was not being done properly for scalar shifts and that
could have led to undefined-value errors being falsely reported in the
obscure case where the shift amount was undefined but the end result
of the shift was unused. This commit handles shifts more in
accordance with the maximally-lazy V-bit-testing scheme used by the
rest of memcheck.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4887 a5019735-40e9-0310-863c-91ae7b9d1cf9
1 file changed