{"push_id":848895474,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d46bcb6b613cb72ecb9f4531c736e1f305948a5e","before":"f111cf25f464e0253fd21f0355426e07dfebeedc","commits":[{"sha":"d46bcb6b613cb72ecb9f4531c736e1f305948a5e","author":{"email":"28f0300aa192bf8c264d7a208db7ef3716f39eab@cs.umn.edu","name":"Stephen McCamant"},"message":"More rules for simplifying shifts that end up as 0\n\nInspired by a situation in some x64 startup code seen on Ubuntu 14.04\nthat was reading from uninitialized memory. When the uninitialized\nmemory is made symbolic, these rules help FuzzBALL see that the symbolic\nvalue is not actually used. Without this you couldn't set -fuzz-start-addr\nwithout also -zero-memory as a workaround.","distinct":true,"url":"https://api.github.com/repos/bitblaze-fuzzball/fuzzball/commits/d46bcb6b613cb72ecb9f4531c736e1f305948a5e"}]}