{"push_id":691228054,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"881c8e0c9ac3eb8d9d20d34b2354ac413f8146b4","before":"708de57fee131ab34a5def889bca7783ab7fd42b","commits":[{"sha":"881c8e0c9ac3eb8d9d20d34b2354ac413f8146b4","author":{"email":"f6f4ad3113690f7f576bf13e93271274145387d1@gmail.com","name":"Alexey Samsonov"},"message":"[GVN] Set proper debug locations for some instructions created by GVN.\n\nDetermining proper debug locations for instructions created in\nPHITransAddr is tricky. We use a simple approach here and simply copy\ndebug locations from instructions computing load address to\n\"corresponding\" instructions re-creating the address computation\nin predecessor basic blocks.\n\nThis may not always be correct, given all the rearrangement and\nsimplification going on, and debug locations may jump around a lot,\nas the basic blocks we copy locations between may be very far from\neach other.\n\nStill, this would work good in most simple cases (e.g. when chain\nof address computing instruction is short, or our mapping turns out\nto be 1-to-1), and we desire to have *some* reasonable debug locations\nassociated with newly inserted instructions.\n\nSee http://reviews.llvm.org/D10351 review thread for more details.\n\nTest Plan: regression test suite\n\nReviewers: spatel, dblaikie\n\nSubscribers: llvm-commits\n\nDifferential Revision: http://reviews.llvm.org/D10351\n\ngit-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@239479 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm/commits/881c8e0c9ac3eb8d9d20d34b2354ac413f8146b4"}]}