{"push_id":1372400901,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"4cdbd20e4e0269fd874b5a3f7d0f9e280b86cd9e","before":"428b70f50ea06da11be107557b4ea963fdf52a36","commits":[{"sha":"bf977933f414635889cf63c3757b37abfde0b7f8","author":{"name":"Kyle Butt","email":"477d37cf5ac939d7e8c2d47b367cf6d6e47a866e@iteratee.net"},"message":"CodeGen: Handle missed case of block removal during BlockPlacement.\n\nThere is a use after free bug in the existing code. Loop layout selects\na preferred exit block, and then lays out the loop. If this block is\nremoved during layout, it needs to be invalidated to prevent a use after\nfree.\n\ngit-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@285348 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/llvm-mirror/llvm/commits/bf977933f414635889cf63c3757b37abfde0b7f8"},{"sha":"0f84babf62b3c369f3cf06adbe7620d41ee5cc6e","author":{"name":"Peter Collingbourne","email":"6214814a67b9688a08e8c6dc7fa5dee076dddc8d@pcc.me.uk"},"message":"BitcodeReader: Require clients to read the block info block at most once.\n\nThis change makes it the client's responsibility to call ReadBlockInfoBlock()\nat most once. This is in preparation for a future change that will allow\nthere to be multiple block info blocks.\n\nSee also: http://lists.llvm.org/pipermail/llvm-dev/2016-October/106512.html\n\nDifferential Revision: https://reviews.llvm.org/D26016\n\ngit-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@285350 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/llvm-mirror/llvm/commits/0f84babf62b3c369f3cf06adbe7620d41ee5cc6e"},{"sha":"4cdbd20e4e0269fd874b5a3f7d0f9e280b86cd9e","author":{"name":"Tim Shen","email":"27d4088a4e3928abba38098f2c71c2e0f4440135@gmail.com"},"message":"[APFloat] Add DoubleAPFloat mode to APFloat. NFC.\n\nSummary:\nThis patch adds DoubleAPFloat mode to APFloat.\n\nNow, an APFloat with semantics PPCDoubleDouble will have DoubleAPFloat layout\n(APFloat.U.Double), which contains two underlying APFloats as\nPPCDoubleDoubleImpl and IEEEdouble semantics. Currently the IEEEdouble APFloat\nis not used, and the first APFloat behaves exactly the same before this change.\n\nThis patch consists of three kinds of logics:\n1) Construction and destruction of APFloat. Now the ctors, dtor, assign\n   opertors and factory functions construct different underlying layout\n   based on the semantics passed in.\n2) s/IEEE/getIEEE()/ for normal, lifetime-unrelated computation functions.\n   These functions only access Floats[0] in DoubleAPFloat, which is the\n   same as today's semantic.\n3) A \"Double dispatch\" function, APFloat::convert. Converting between two\n   different layouts requires appropriate logic.\n\nNeither of these change the external behavior.\n\nReviewers: hfinkel, kbarton, echristo, iteratee\n\nSubscribers: mehdi_amini, llvm-commits\n\nDifferential Revision: https://reviews.llvm.org/D25977\n\ngit-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@285351 91177308-0d34-0410-b5e6-96231b3b80d8","distinct":true,"url":"https://api.github.com/repos/llvm-mirror/llvm/commits/4cdbd20e4e0269fd874b5a3f7d0f9e280b86cd9e"}]}
{"actor":{"display_login":"llvm-mirror"}}