{"push_id":3039244553,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"97c9cb487b28161a2ac78a9f296099db329be61b","before":"89553c7dfe81a7dd96e5ebec518fbafb6def2e91","commits":[{"sha":"97c9cb487b28161a2ac78a9f296099db329be61b","author":{"name":"Philip Reames","email":"1a6d70c497b881333962fb40612e3f3827d7c1cd@philipreames.com"},"message":"[GCRoot] Remove some unneccessary complexity\n\nThe GCStrategy provides three configuration options were are largely redundant.\n\n1) Support for conditionally lowering gcread and gcwrite to loads and stores.  This is redundant since any GC which wished to use these abstractions would lower them out of existance before the built in lowering anyways.  As such, there's no need to have the lowering being conditional.\n2) Conditional initialization for allocas marked via gcroot.  Semantically, roots have to be initialized before first potential use.  Arguably, the frontend really should have responsibility for that, but the old API allowed the frontend to ignore this detail.  Only one builtin GC used the non-initializing mode.  Since no one to my knowledge actually uses the ErlangGC strategy, I decide the slight pessimization was worth the simplicity.  If that turns out to be problematic, we can always improve the insertion algorithm to detect more existing initializing stores.","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project-20170507/commits/97c9cb487b28161a2ac78a9f296099db329be61b"}]}
{"actor":{"display_login":"chapuni"}}