[PATCH 0/2] compiling with -fsanitize=undefined

I was playing around with the new-ish "-fsanitize=undefined" compiler flag, and it detected a few problems: 1. We sometimes bit-shift signed constants too far (fixed by the first patch). 2. We have some unaligned memory accesses that presumably work OK on x86, but would blow up on

Re: [PATCH 0/2] compiling with -fsanitize=undefined

On Tue, Dec 29, 2015 at 01:34:49AM -0500, Jeff King wrote: > 2. We have some unaligned memory accesses that presumably work OK on > x86, but would blow up on ARM or other platforms (I didn't test). > > The latter looks like it's in the untracked cache code (Duy and > Christian cc'd).