{"push_id":2823594228,"size":33,"distinct_size":33,"ref":"refs/heads/master","head":"ad7bbdfbd6dea02acb1755aa1fa38181137580e2","before":"809764f2c914c3e178bc6d90a255b3bf83b61009","commits":[{"sha":"ff684523018e3dae6445898962581ac8dfc4971c","author":{"name":"Alex Hoppen","email":"681b7f649f4b7bb960be2ae1949b558cd9dffe3b@apple.com"},"message":"[swiftBasic] Introduce an exponentially growing appending binary stream\n\nIt is more efficient than llvm::AppendingBinaryByteStream if a lot of\nsmall data gets appended to it because it doesn't need to resize its\nbuffer on each write.","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/ff684523018e3dae6445898962581ac8dfc4971c"},{"sha":"491b11c73c92306d2d5543a6d1f145f6cebe600d","author":{"name":"Alex Hoppen","email":"681b7f649f4b7bb960be2ae1949b558cd9dffe3b@apple.com"},"message":"[SourceKit] Use the exponential growth binary stream to write the syntax tree","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/491b11c73c92306d2d5543a6d1f145f6cebe600d"},{"sha":"49f2e14094098505d8b1bc3fb073975aafefee6a","author":{"name":"Alex Hoppen","email":"681b7f649f4b7bb960be2ae1949b558cd9dffe3b@apple.com"},"message":"[swiftBasic] Use a SmallVector as the underlying storage for ExponentialGrowthAppendingBinaryByteStream","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/49f2e14094098505d8b1bc3fb073975aafefee6a"},{"sha":"fcfd4c8a8c18d7fb4295fc523d9ef382bacf4b0f","author":{"name":"Doug Gregor","email":"20237f4b434bdcccb3b4c7b8643e049a656bb565@apple.com"},"message":"[Type checker] Introduce a request to evaluate “where” clause requirements.\n\nIntroduce a new form of request that produces the ith Requirement of the\nwhere clause of a given entity, which could be a protocol, associated type,\nor anything with generic parameters. The requirement can be evaluated\nat any type resolution stage; the “interface” type stage will be cached\nin the existing RequirementReprs.\n\nFixes SR-8119 / rdar://problem/41498944.","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/fcfd4c8a8c18d7fb4295fc523d9ef382bacf4b0f"},{"sha":"94951f431d3c009648be68d388f6a5c4cc4b6228","author":{"name":"Doug Gregor","email":"20237f4b434bdcccb3b4c7b8643e049a656bb565@apple.com"},"message":"[Lazy resolver] Remove resolveTrailingWhereClause().\n\nThis is completely subsumed by the “requirement” request.\nAlso remove some dead declarations in TypeChecker. NFC.","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/94951f431d3c009648be68d388f6a5c4cc4b6228"},{"sha":"6ba45473dfe574d32b35ed2b247142f078e4a7b0","author":{"name":"Erik Eckstein","email":"f1682ebb83d0ce00b2767a78fc8ea26a8af24e40@apple.com"},"message":"Remove the pinning addressors\n\nIt was used for Array + related types.\nWith exclusivity checking the pinned addressors are not useful anymore.\n\nrdar://problem/35401528","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/6ba45473dfe574d32b35ed2b247142f078e4a7b0"},{"sha":"192431b8307bbace2ae1702e19bc8140da5b88a7","author":{"name":"Erik Eckstein","email":"f1682ebb83d0ce00b2767a78fc8ea26a8af24e40@apple.com"},"message":"SIL optimizer: remove the RemovePin optimization.\n\nNot useful anymore after removing the pinning adressors","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/192431b8307bbace2ae1702e19bc8140da5b88a7"},{"sha":"7c06d4f8abeffa312ae81f21897d4b20dd3f7d58","author":{"name":"Erik Eckstein","email":"f1682ebb83d0ce00b2767a78fc8ea26a8af24e40@apple.com"},"message":"Remove the pinning built-ins.\n\nThey are not used anymore after removing the pinning adressors.","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/7c06d4f8abeffa312ae81f21897d4b20dd3f7d58"},{"sha":"99a9ed5535907bdbc333c0b60f07f3f93d260fa5","author":{"name":"Erik Eckstein","email":"f1682ebb83d0ce00b2767a78fc8ea26a8af24e40@apple.com"},"message":"SIL: remove the pinning instructions: strong_pin, strong_unpin, is_unique_or_pinned\n\nThey are not used anymore after removing the pinning addressors.","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/99a9ed5535907bdbc333c0b60f07f3f93d260fa5"},{"sha":"7e96f123b93de05b4415d478cef0c2065b887b4d","author":{"name":"Doug Gregor","email":"20237f4b434bdcccb3b4c7b8643e049a656bb565@apple.com"},"message":"[Type checker] Make sure we check access of ‘where’ clauses properly.","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/7e96f123b93de05b4415d478cef0c2065b887b4d"},{"sha":"5e2f3d8448f67d92e1d3b215dd5383754291eb61","author":{"name":"Joe Shajrawi","email":"158f315d74d5919719d0acb1596dd2ac8a476fa3@apple.com"},"message":"[LICM]: support hosting ref_element_addr even if they are not guaranteed to be executed\n\nIn some instances, some instructions, like ref_element_addr, can be hoisted outside of loops even if they are not guaranteed to be executed.\n\nWe currently don’t support that / bail. We only try to do so / do further analysis only for begin_access because they are extremely heavy.\n\nHowever, we need to support hosting of ref_element_addr in that case, if it does not have a loop dependent operand, in order to be able to hoist begin_access instructions in some benchmarks.\n\nInitial local testing shows that this PR, when we enable exclusivity, improves the performance of a certain internal benchmark by over 40%\n\nSee rdar://problem/43623829","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/5e2f3d8448f67d92e1d3b215dd5383754291eb61"},{"sha":"868f763406b99a2ff2243cabb830589c16dbd60e","author":{"name":"Doug Gregor","email":"20237f4b434bdcccb3b4c7b8643e049a656bb565@apple.com"},"message":"[GSB] Ensure that we don’t pick a self-recursive requirement source.\n\nWhen computing the conformance access path, make sure that we don’t pick\na self-recursive requirement source.","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/868f763406b99a2ff2243cabb830589c16dbd60e"},{"sha":"3c54886c4df0c92c882d99001537001e339bcf47","author":{"name":"Doug Gregor","email":"20237f4b434bdcccb3b4c7b8643e049a656bb565@apple.com"},"message":"[Type checker] Use RequirementRequest::visitRequirements() more intentionally.\n\nRather than using RequirementRequest::visitRequirements() for its side\neffects, then reading from the TypeLocs left behind, start eliminating\nTypeLoc-based APIs so we pass Type and TypeRepr separately.\n\nAdd some utilities to dig into a possibly-null RequirementRepr* and dig\nout the appropriate TypeReprs.","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/3c54886c4df0c92c882d99001537001e339bcf47"},{"sha":"5dfeb4c8cf798f8933b2be1ae058283a4388628d","author":{"name":"Jordan Rose","email":"fb557bf086ed2b11438cabe542327e0fb845e545@apple.com"},"message":"[ModuleInterface] Don't setAddedImplicitInitializers() in Parse (#18933)\n\n...wait until Sema. Parse shouldn't be messing with Sema-level\r\nproperties in the decls it builds.\r\n\r\nNo functionality change.","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/5dfeb4c8cf798f8933b2be1ae058283a4388628d"},{"sha":"46bfebc49f4ea73ebd4851e039da28538c3b639b","author":{"name":"eeckstein","email":"f1682ebb83d0ce00b2767a78fc8ea26a8af24e40@apple.com"},"message":"Merge pull request #18922 from eeckstein/remove-pinning\n\nRemove the Array pinning addressor and all the pinning instructions in SIL","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/46bfebc49f4ea73ebd4851e039da28538c3b639b"},{"sha":"04b5eb501dc4329cf7cd0fa50bb2e77f105dee59","author":{"name":"swift-ci","email":"ae1c7a81971cd87243eb6e815ca4a320961564e9@users.noreply.github.com"},"message":"Merge pull request #18931 from shajrawi/licm_refelem","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/04b5eb501dc4329cf7cd0fa50bb2e77f105dee59"},{"sha":"eeb8f330f92fcde83b6549aee7d04fbde3d7a9e5","author":{"name":"Jordan Rose","email":"fb557bf086ed2b11438cabe542327e0fb845e545@apple.com"},"message":"[ModuleInterface] Allow conformances to be missing value witnesses (#18932)\n\nIt's not clear whether we'll actually need this feature in the long\r\nrun, but we certainly need it now because non-@usableFromInline\r\nmembers can (currently) satisfy public requirements when a\r\n@usableFromInline internal type conforms to a public protocol. In\r\nthese cases, we'll treat the witnesses as present but opaque, and\r\nclients will perform dynamic dispatch when using them even when\r\na generic function gets specialized.\r\n\r\nWith this, we're able to generate a textual interface for the standard\r\nlibrary, compile it back to a swiftmodule, and use it to build a Hello\r\nWorld program!","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/eeb8f330f92fcde83b6549aee7d04fbde3d7a9e5"},{"sha":"12b6c0a7a74802ba1ac38f9ab47be3e6c3be2fa3","author":{"name":"Erik Eckstein","email":"f1682ebb83d0ce00b2767a78fc8ea26a8af24e40@apple.com"},"message":"SIL Optimizer: fix a crash in constant folding.\n\nWhen the folded instructions are in an unreachable CFG loop, there may be loops in the use-def chain (there is no defined dominance order).\nWe have to handle this special case.\n\nrdar://problem/43530134","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/12b6c0a7a74802ba1ac38f9ab47be3e6c3be2fa3"},{"sha":"249b55bf3144a0675054b6f64bc3c7a3814f5ac1","author":{"name":"swift-ci","email":"ae1c7a81971cd87243eb6e815ca4a320961564e9@users.noreply.github.com"},"message":"Merge pull request #18939 from eeckstein/fix-cf-crash","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/249b55bf3144a0675054b6f64bc3c7a3814f5ac1"},{"sha":"dd2f3b43860d7a49e4140c0f4a06217c2fd4829d","author":{"name":"Ben Cohen","email":"f6358031b01ba395cdd151dcadd901fffc88c517@users.noreply.github.com"},"message":"[stdlib] More inalienable auditing (#18925)\n\n* Removing FIXME from methods also marked always/never\r\n\r\n* Unavailable/deprecated things don't need inlining\r\n\r\n* Trivial implementations\r\n\r\n* Enum namespaces\r\n\r\n* Unsafe performance of opaque/raw pointer\r\n\r\n* Dump doesn't need to be fast\r\n\r\n* Error paths shouldn't require inlining\r\n\r\n* Consistency with surrounding code\r\n\r\n* Lazy performance needs specialization","distinct":true,"url":"https://api.github.com/repos/aschwaighofer/swift/commits/dd2f3b43860d7a49e4140c0f4a06217c2fd4829d"}]}
{"actor":{"display_login":"aschwaighofer"}}