{"push_id":1405092685,"size":7,"distinct_size":7,"ref":"refs/heads/upstream-with-swift","head":"81e3448166e726ba2ac0a491923852e629a7a161","before":"b89805d3055fb72ccfc0a91d6f20897be69aa72c","commits":[{"sha":"3b544c6cc98dd653ddb9ec6963929c5b9e937db5","author":{"name":"Reid Kleckner","email":"52b754ec9164ffe1549cbed996e28ab476b86804@google.com"},"message":"[asan] Don't assert that a target is within 2GB on 32-bit Windows\n\nSummary:\nIn a 32-bit address space, PC-relative jump targets are wrapped, so a\ndirect branch at 0x90000001 can reach address 0x10000000 with a\ndisplacement of 0x7FFFFFFFF. This can happen in applications, such as\nChrome, that are linked with /LARGEADDRESSAWARE.\n\nReviewers: etienneb\n\nSubscribers: mgorny, llvm-commits\n\nDifferential Revision: https://reviews.llvm.org/D26650\n\ngit-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@286997 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/gottesmm/swift-compiler-rt/commits/3b544c6cc98dd653ddb9ec6963929c5b9e937db5"},{"sha":"04ffe3d34b50ba620c4d007ecfcd463866290a1a","author":{"name":"Reid Kleckner","email":"52b754ec9164ffe1549cbed996e28ab476b86804@google.com"},"message":"[asan] Reduce prototype duplication with decltype\n\nNFC\n\ngit-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@287000 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/gottesmm/swift-compiler-rt/commits/04ffe3d34b50ba620c4d007ecfcd463866290a1a"},{"sha":"e24f588d0a6362a49854d0f78ec9ce92535ac4ed","author":{"name":"Kuba Brecka","email":"893b177b5ee228ca872c6fece652e12874c3943c@gmail.com"},"message":"[tsan] Call pthread interceptors directly in TSan RTL unit tests\n\nOn Darwin, we're running the TSan unit tests without interceptors. To make sure TSan observes all the pthread events (thread creating, thread join, condvar signal, etc.) in tsan_posix.cc, we should call the pthread interceptors directly, as we already do in tsan_test_util_posix.cc. This fixes some flaky failures on Darwin bots.\n\nDifferential Revision: https://reviews.llvm.org/D26639\n\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@287026 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/gottesmm/swift-compiler-rt/commits/e24f588d0a6362a49854d0f78ec9ce92535ac4ed"},{"sha":"ccee12bafd8de1ef96bca677075805b50c3393db","author":{"name":"Kuba Brecka","email":"893b177b5ee228ca872c6fece652e12874c3943c@gmail.com"},"message":"[asan] Re-enable the use-after-scope-types.cc test on Darwin, now that r287028 fixed the llvm-symbolizer issue that broke this test.\n\nDifferential Revision: https://reviews.llvm.org/D26537\n\n\n\ngit-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@287029 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/gottesmm/swift-compiler-rt/commits/ccee12bafd8de1ef96bca677075805b50c3393db"},{"sha":"ec301129e76d82fbdf59168f7478b343cff71294","author":{"name":"Reid Kleckner","email":"52b754ec9164ffe1549cbed996e28ab476b86804@google.com"},"message":"Allow users to call ASan's deadly exception report mechanism\n\nUsers often have their own unhandled exception filters installed. ASan\nalready goes to great lengths to install its own filter, but our core\nwars with Chrome crashpad have escalated to the point that its time to\ndeclare a truce. By exposing this hook, they can call us directly when\nthey want ASan crash reporting without worrying about who initializes\nwhen.\n\ngit-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@287040 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/gottesmm/swift-compiler-rt/commits/ec301129e76d82fbdf59168f7478b343cff71294"},{"sha":"a1df33d42314dc8c52e3eb5254f0f216397e60fc","author":{"name":"Dean Michael Berris","email":"6b0af69dd05a094d46606b1b8f141285184892b2@google.com"},"message":"[XRay][compiler-rt] Disable XRay instrumentation of the XRay runtime.\n\nSummary:\nAdds a CMake check for whether the compiler used to build the XRay\nlibrary supports XRay-instrumentation. If the compiler we're using does\nsupport the `-fxray-instrument` flag (i.e. recently-built Clang), we\ndefine the XRAY_NEVER_INSTRUMENT macro that then makes sure that the\nXRay runtime functions never get XRay-instrumented.\n\nThis prevents potential weirdness involved with building the XRay\nlibrary with a Clang that supports XRay-instrumentation, and is\nattempting to XRay-instrument the build of compiler-rt.\n\nReviewers: majnemer, rSerge, echristo\n\nSubscribers: mehdi_amini, llvm-commits, mgorny\n\nDifferential Revision: https://reviews.llvm.org/D26597\n\ngit-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@287068 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/gottesmm/swift-compiler-rt/commits/a1df33d42314dc8c52e3eb5254f0f216397e60fc"},{"sha":"81e3448166e726ba2ac0a491923852e629a7a161","author":{"name":"Automerger","email":"8998fc788b2c7d9eadbe946283f5b8370e9b572a@Swift"},"message":"Propagating prior merge from 'llvm.org/master'.","distinct":true,"url":"https://api.github.com/repos/gottesmm/swift-compiler-rt/commits/81e3448166e726ba2ac0a491923852e629a7a161"}]}
{"actor":{"display_login":"gottesmm"}}