{"push_id":2299824363,"size":1,"distinct_size":0,"ref":"refs/heads/upstream/master","head":"7a8e626f21921c75c04088c8ec0874c668256ade","before":"f61575826a1eef7d0c0198d6f444894ec72ea394","commits":[{"sha":"7a8e626f21921c75c04088c8ec0874c668256ade","author":{"name":"Artem Dergachev","email":"9c257a9f5889b207f966593fb6de1d6fc101973e@gmail.com"},"message":"[analyzer] Don't communicate evaluation failures through memregion hierarchy.\n\nWe use CXXTempObjectRegion exclusively as a bailout value for construction\ntargets when we are unable to find the correct construction region.\nSometimes it works correctly, but rather accidentally than intentionally.\n\nNow that we want to increase the amount of situations where it works correctly,\nthe first step is to introduce a different way of communicating our failure\nto find the correct construction region. EvalCallOptions are introduced\nfor this purpose.\n\nFor now EvalCallOptions are communicating two kinds of problems:\n- We have been completely unable to find the correct construction site.\n- We have found the construction site correctly, and there's more than one of\n  them (i.e. array construction which we currently don't support).\n\nAccidentally find and fix a test in which the new approach to communicating\nfailures produces better results.\n\nDifferential Revision: https://reviews.llvm.org/D42457\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@324018 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":false,"url":"https://api.github.com/repos/fuchsia-mirror/third_party-clang/commits/7a8e626f21921c75c04088c8ec0874c668256ade"}]}
{"actor":{"display_login":"FF0080"}}