{"push_id":741657919,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"7a641cc94099f384ed8f918322288a7a0fbbd0ba","before":"8ad735a538bda0ca42a18d4e6917d54e6dedb290","commits":[{"sha":"7a641cc94099f384ed8f918322288a7a0fbbd0ba","author":{"email":"4a8dfeb3a1c6b90c15fd5a5a91e8e25ea46ffe0b@rotateright.com","name":"Sanjay Patel"},"message":"move DAGCombiner's allowableAlignment() helper function into the TLI\n\nMaking allowableAlignment() more accessible was suggested as a predecessor patch\nfor D10662, so I've pulled it into TargetLowering. This let's us remove 4 instances\nof duplicate logic in LegalizeDAG.\n\nThere's a subtle functional change in the implementation: the existing \nallowableAlignment() code was using getPrefTypeAlignment() when checking \nalignment with the DataLayout and assumed that was fast. In this implementation,\nwe use getABITypeAlignment() and assume that is fast. See the TODO comment or the\ndiscussion in the Phab review for future improvements in this implementation\n(don't use the data layout at all).\n\nThere are no regression test changes from this difference, and I'm not sure how to\nexpose it via a test. I think we actually do want to provide the 'Fast' param when\nchecking this from DAGCombiner::MergeConsecutiveStores(). Ie, we shouldn't merge \nstores if the new stores are not going to be fast. But that change will require \nfixing allowsMisalignedMemoryAccess() overrides as noted in D10662.\n\nDifferential Revision: http://reviews.llvm.org/D10905\n\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@243549 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm/commits/7a641cc94099f384ed8f918322288a7a0fbbd0ba"}]}