{"push_id":2783175814,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"153d620e3ea97f5ebf4484a4077f9f60e25ba335","before":"c1477079b39594d0d053cfbdbe52139394cb9c7f","commits":[{"sha":"153d620e3ea97f5ebf4484a4077f9f60e25ba335","author":{"name":"Vedant Kumar","email":"004c457a2ebaecf18123fd2614baa1d571fe5234@apple.com"},"message":"[IRMemoryMap] Shrink Allocation and make it move-only (NFC)\n\nProfiling data show that Allocation::operator= is hot (see the data\nattached to the Phab review).\n\nReorder a few fields within Allocation to avoid implicit structure\npadding and shrink the structure. This should make copies a bit cheaper.\n\nAlso, given that an Allocation contains a std::vector (by way of\nDataBufferHeap), it's preferable to make it move-only instead of\npermitting expensive copies. As an added benefit this allows us to have\na single Allocation constructor instead of two.\n\nDifferential Revision: https://reviews.llvm.org/D50271","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project-submodule/commits/153d620e3ea97f5ebf4484a4077f9f60e25ba335"}]}
{"actor":{"display_login":"chapuni"}}