{"push_id":1454635747,"size":2,"distinct_size":2,"ref":"refs/heads/global-addr-safety-spaghetti","head":"192cc9de863861bf7bd85fcb18aa913ccd59b96b","before":"1f42eddad16831a1be6c9a259a27ab97a0eea5a5","commits":[{"sha":"7e276dd08d42e99eefbbde771e369f0631916d16","author":{"name":"Zvonimir","email":"ed4e6a18237b90322dcc90d858039f5f51985faf@cs.utah.edu"},"message":"Enforced proper memory safety checking for globals\n\nOur memory safety conditions were not handling globals properly\nsince nothing was being checked for negative addresses. I removed\nthat part from our memory safety assertions so that globals\nare properly checked as well.","distinct":true,"url":"https://api.github.com/repos/smackers/smack/commits/7e276dd08d42e99eefbbde771e369f0631916d16"},{"sha":"192cc9de863861bf7bd85fcb18aa913ccd59b96b","author":{"name":"Zvonimir","email":"ed4e6a18237b90322dcc90d858039f5f51985faf@cs.utah.edu"},"message":"Added padding between globals to catch memory safety errors\n\nGlobals were packed tightly together, which means that overflows\nwould jump into the adjacent globals and memory safety error would\nnot get reported. Now I added padding of 1024 bytes between globals,\nwhich should help with this, even though it is not a completely\nsound solution.\n\nFixes #190","distinct":true,"url":"https://api.github.com/repos/smackers/smack/commits/192cc9de863861bf7bd85fcb18aa913ccd59b96b"}]}
{"actor":{"display_login":"zvonimir"}}