Skip to main content

Browse the archive

https://github.com/apple/swift
06 April 2024, 01:41:40 UTC
sort by:
Revision Author Date Message Commit Date
8cd7559 Dario Rexin 28 January 2022, 23:09:38 UTC Update README.md 28 January 2022, 23:09:38 UTC
f3fd462 Mishal Shah 27 January 2022, 09:06:13 UTC Merge pull request #41031 from apple/update-swift-version-5.5.3 Bump the Swift version to 5.5.3 27 January 2022, 09:06:13 UTC
78784a6 Mishal Shah 27 January 2022, 01:33:37 UTC Bump the Swift version to 5.5.3 27 January 2022, 01:33:37 UTC
b5f30b5 Mishal Shah 24 January 2022, 23:36:46 UTC Merge pull request #40540 from DougGregor/task-group-atomic-fix-5.5 use `compare_exchange_strong` to protect agianst spurious failures 24 January 2022, 23:36:46 UTC
9ce28ed Mishal Shah 24 January 2022, 18:28:55 UTC [5.5] Fix one test and disable two tests for Linux aarch64 (#40427) * Disable lto-autolink test on linux-aarch64 (cherry picked from commit d3ff2b19dc64d69ab683d000270d79bb3ebd7059) * [Linux] XFAIL typeref_decoding_asan test on linux-aarch64 (#37000) ASan seems to cause reflection information to not be extractable from binaries on aarch64. rdar://76975976 (cherry picked from commit 8aae5c52fb5a41b2572c7a56ddc79be2b213f93c) * [Linux] Add symbol to ignore list in symbol-visibility-linux test (#37001) This test fails on linux-aarch64 because of the additional weak C++ symbol (cherry picked from commit fe7ade852f7819795cfdc9bf028d4ba03a28b8e0) Co-authored-by: Dario Rexin <dario.rexin@me.com> 24 January 2022, 18:28:55 UTC
e06fced Jay Choi 24 January 2022, 18:27:35 UTC [cmake] [unittests] remove unnecessary scripts (#40279) gtest, gtest_main LINK_LIBRARIES dependencies changed by that removed scripts to absolute library file path. as a result losing necessary include path dirs. 24 January 2022, 18:27:35 UTC
8e8b9a1 Mishal Shah 22 January 2022, 01:03:16 UTC Merge pull request #40929 from compnerd/5.5.3-unicode [5.5] stdlib: change the console to UTF-8 on start 22 January 2022, 01:03:16 UTC
83ce537 Saleem Abdulrasool 20 January 2022, 22:49:06 UTC Update async_taskgroup_is_asyncsequence.swift 20 January 2022, 22:49:06 UTC
0a91c7f Saleem Abdulrasool 20 January 2022, 22:48:41 UTC Update async_taskgroup_asynciterator_semantics.swift 20 January 2022, 22:48:41 UTC
250fac5 Saleem Abdulrasool 20 January 2022, 21:07:42 UTC Update async_taskgroup_throw_rethrow.swift Enable the test that was previously failing on 5.5. This has been stable on main for a while, and seems to also be now passing on 5.5 20 January 2022, 21:07:42 UTC
80ccccd Saleem Abdulrasool 19 December 2021, 23:33:45 UTC stdlib: change the console to UTF-8 on start This adjusts the Windows console to switch the codepage to UTF-8. This is important as the default codepage (CP437) does not allow for UTF-8 output, but expects ASCII. However, strings in Swift are assumed to be UTF-8, which means that there is now a conversion mismatch. Because the console mode persists beyond the duration of the application as it is state local to the console and not the C runtime, we should restore the state of the console before termination. We do this by registering a termination handler via `atexit`. This means that an abnormal termination (e.g. via `fatalError`) will irrevocably alter the state of the console (interestingly enough, `chcp` will still report the original console codepage even though the console will internally be set to UTF-8). Fixes: SR-13807 (cherry picked from commit 9847cab8d3e5b74101a54bd3871f5002ffaf688c) 20 January 2022, 18:02:44 UTC
6ad300d najacque 18 January 2022, 18:49:54 UTC Merge pull request #40858 from DougGregor/back-deployed-concurrency-no-arm64e-5.5 [5.5] Don't build arm64e slices of the back-deployed libswift_Concurrency.dylib 18 January 2022, 18:49:54 UTC
bead2cd Doug Gregor 14 January 2022, 20:03:03 UTC Don't build arm64e slices of the back-deployed libswift_Concurrency.dylib. The arm64e ABI is not stable, so there is no reason to build or ship arm64e slices of the back-deployed libswift_Concurrency.dylib. Moreover, these slices interact poorly with bitcode_strip tool, resulting in a shared library that iOS will refuse to load in certain circumstances. Fixes rdar://85752735 / FB9780976. Thank you to Jay Muthialu and Keith Smiley for helping debug this issue! 14 January 2022, 20:08:27 UTC
e6979d2 Doug Gregor 11 January 2022, 17:56:33 UTC Merge pull request #40044 from etcwilde/ewilde/5.5/fix-weak-extendedFramePointerFlags 5.5 fix weak extended frame pointer flags 11 January 2022, 17:56:33 UTC
5a3e0b3 Konrad `ktoso` Malawski 06 January 2022, 22:12:58 UTC Merge pull request #40750 from ktoso/pick-55-tbd-fix 🍒 [5.5] Add Initializers' AFPs 06 January 2022, 22:12:58 UTC
f506e54 Nate Chandler 18 August 2021, 01:32:01 UTC [TBD] Add initializers AFPs to TBD. Previously, the async function pointers for initializers were omitted from TBD files. That resulted in a mismatch between the symbols exported from the IR module and those listed in the TBDS. Here, that is corrected. As with regular function pointers, the symbols for the async function pointers for initializers need to be manually added just as the symbols for initializers themselves need to be manually added. rdar://82045176 06 January 2022, 03:00:08 UTC
36922aa Nate Chandler 18 August 2021, 01:29:04 UTC [TBD] Pass decl ref when adding AFP symbols. Previously, adding a symbol for an async function pointer to the TBD entailed passing an AbstractFunctionDecl to TBDGenVisitor::addAsyncFunctionPointerSymbol. That arrangment limited clients from specifying a different SILDeclRef::Kind than the one which could be inferred from the type of the decl which was passed to the visitor's function. In particular, it prevented clients from specifying that the symbol for an initializer corresponding to a ConstructorDecl should be added to the TBD. Here, the arrangement is changed so that the visitor's function takes a SILDeclRef. 06 January 2022, 03:00:04 UTC
16ff49c Nate Chandler 18 August 2021, 01:23:58 UTC [IRGen] Give decl ref to LinkEntity::forAFP. Previously, a LinkEntity for an AST async function pointer was built by passing an AbstractFunctionDecl. Later, decl was used to construct a SILDeclRef. That arrangement meant that clients could not construct such a LinkEntity whose SILDeclRef::Kind could not be inferred from the dynamic type of the decl from which the SILDeclRef was constructed. In particular, clients could not construct a LinkEntity for the initializer corresponding to a ConstructorDecl. Here, the arrangment is changed so that the LinkEntity for an AST async function pointer is built by passing a SILDeclRef. 06 January 2022, 03:00:00 UTC
a90c721 Kavon Farvardin 19 November 2021, 00:15:47 UTC use `compare_exchange_strong` to protect agianst spurious failures A `compare_exchange_weak` can spuriously return false, regardless of whether a concurrent access happened. This was causing a null-pointer dereference in TaskGroupImpl::poll in a narrow circumstance. The dereference failure only appears when using the `arm64` slice of the runtime library, since Clang will use `ldxr/stxr` for synchronization on such targets. The weak form does not retry on a spurious failure, but the strong version will. resolves rdar://84192672 (cherry picked from commit 69e80a1201636e124451de946dfa7fc255bf05ca) 14 December 2021, 03:36:53 UTC
c1776ee Doug Gregor 07 December 2021, 22:37:50 UTC Merge pull request #40451 from compnerd/ret-void [5.5] Cherry-pick a change from main to handle missing mandatory tail call optimizations 07 December 2021, 22:37:50 UTC
ef1fbfd Mishal Shah 07 December 2021, 16:00:33 UTC Merge pull request #40445 from apple/bump-swift-version-5.5.2 Bump the Swift version to 5.5.2 07 December 2021, 16:00:33 UTC
9fbf41c Saleem Abdulrasool 07 December 2021, 05:32:02 UTC test: repair the IRGen tests after #39680 The change in 39680 impacts more than WebAssembly, but it did not update the tests for impacted targets. (cherry picked from commit 3df2531cd50ba5d4c373a2e6a35805fd9b351b59) 07 December 2021, 15:41:26 UTC
8079b35 Yuta Saito 11 October 2021, 11:13:05 UTC [IRGen] Put 'ret void' instead of unreachable for non swiftasync cc If target doesn't support musttail (e.g. WebAssembly), the function passed to coro.end.async can return control back to the caller. So the frontend should emit 'ret void' instead of unreachable after the coro.end.async intrinsic call to allow such situation. (cherry picked from commit 671ce74e97ed4f69aad0aa71afcc46408f337d12) 07 December 2021, 15:40:37 UTC
fddc7e3 Mishal Shah 07 December 2021, 03:32:42 UTC Bump the Swift version to 5.5.2 07 December 2021, 03:32:42 UTC
2c007d8 Saleem Abdulrasool 03 December 2021, 20:16:01 UTC IRGen: use the accessor conformance on Windows (#40264) When building with lazy initialization of the root conformance, we need to ensure that we are invoking the accessor to initialize the conformance record. We would previously generate a direct reference to the conformance, which was uninitialized, resulting in a crash at runtime. The non-windows test changes here are to use/imply static linking for the support modules. This should have no difference on the non-Windows targets, but makes a difference on Windows where this implies that everything will be built into a single module, which permits the non-indirect access to types. Unfortunately, this does somewhat regress the test coverage on Windows as we do not exercise as much of the shared linkage paths which do change some of the code-generation to deal with the moral equivalent of the GOT - the IAT. Special thanks to @slavapestov for the pointer to `isDependentConformance`. This should eliminate the last known issue with cross-module protocol conformances. Fixes: SR-14807 The 5.5-only test changes are due to the lack of support for static linking which means that all the support modules are treated as though they are behind a resiliency boundary on Windows. We relax the tests to accept both though on main we do not do so. 03 December 2021, 20:16:01 UTC
9026b6e Saleem Abdulrasool 03 December 2021, 20:13:04 UTC Concurrency: fix UB in DefaultActor initialization (#40263) This fixes a latent UB instance in the `DefaultActor` implementation that has haunted the Windows target. The shared constructor for the type caused an errant typo that happened to compile which introduced UB but happened to work for the non-Windows cases. This happened to work for the other targets as `swift::atomic` had a `std::atomic` at on most configurations, and the C delegate for the Actor initializer happened to overlap and initialize the memory properly. The Windows case used an inline pointer width value but would be attempted to be initialized as a `std::atomic`. Relying on the overlap is unsafe to assume, and we should use the type's own constructor which delegates appropriately. 03 December 2021, 20:13:04 UTC
424bc40 Doug Gregor 17 November 2021, 23:57:42 UTC Merge pull request #40046 from etcwilde/ewilde/5.5/handle-missing-getMainExecutor-decl 5.5: Workaround to cope with older SDKs 17 November 2021, 23:57:42 UTC
f0c5c4b Evan Wilde 16 November 2021, 19:47:54 UTC Conjure up `asyncMainDrainQueue` The asyncMainDrainQueue is also declared `internal`, so it won't show up in the swiftinterface file. The expected declaration is: ``` @available(SwiftStdlib 5.5, *) @_silgen_name("swift_task_asyncMainDrainQueue") internal func _asyncMainDrainQueue() -> Never ``` 16 November 2021, 20:01:57 UTC
2133aa7 Evan Wilde 27 October 2021, 19:17:53 UTC Add `_getMainExecutor` The `getMainExecutor` was declared internal so it doesn't show up in the swift interface files. The definition exists though. The missing declaration causes the compiler to crash while compiling programs with async-main since it can't find the declaration. This patch changes it to conjure up the appropriate decl if it can't find it. 16 November 2021, 20:00:28 UTC
5d24d97 Alexis Laferrière 16 November 2021, 04:14:00 UTC [Sema] Generate TRC for unparsed functions right before type-checking (#40126) Fix an issue where `if #available(...)` conditions were ignored in emit-module-separately builds or when skipping non-inlinable function bodies. To handle functions for which parsing is delayed but type-checking is not delayed, move up building the delayed TRC to the TypeCheckFunctionBodyRequest service. rdar://85265934 16 November 2021, 04:14:00 UTC
476f634 Saleem Abdulrasool 15 November 2021, 20:43:51 UTC Merge pull request #40147 from compnerd/5.5-async-function-protocol [5.5] async function pointer support for Windows 15 November 2021, 20:43:51 UTC
6fa7650 Ben Barham 14 November 2021, 06:17:04 UTC Merge pull request #40148 from bnbarham/cherry-rdar83780222 [5.5][Index] Add an async symbol property for async functions 14 November 2021, 06:17:04 UTC
814f8b8 Saleem Abdulrasool 12 November 2021, 17:51:32 UTC Update class_resilience.swift Make the test less restrictive. The value of the select is not referenced, no need to match it. 12 November 2021, 17:51:32 UTC
e20e420 Ben Barham 20 October 2021, 02:19:16 UTC [Index] Add an async symbol property for async functions Resolves rdar://83780222 12 November 2021, 02:04:39 UTC
3ee2b89 Saleem Abdulrasool 01 November 2021, 22:37:25 UTC Update async-inheritance.swift Tweak test for macOS (cherry picked from commit fee023cac2f1d8d9c078d333202c0268fabaf79e) 12 November 2021, 01:14:13 UTC
1554b9c Saleem Abdulrasool 01 November 2021, 00:01:00 UTC IRGen: initial pass to support `async` inheritance on Windows With PE/COFF, one cannot reference a data symbol directly across the binary module boundary. Instead, the reference must be indirected through the Import Address Table (IAT) to allow for position independence. When generating a reference to a AsyncFunctionPointer ({i8*, i32}), we tag the pointer as being indirected by tagging bit 1 (with the assumption that native alignment will ensure 4/8 byte alignment, freeing the bottom 2 bits at least for bit-packing). We tweak the v-table/witness table emission such that all references to the AsyncFunctionPointer are replaced with the linker synthetic import symbol with the bit packing: ~~~ .quad __imp_$s1L1CC1yyYaKFTu+1 ~~~ rather than ~~~ .quad $s1L1CC1yyYaKFTu ~~~ Upon access of the async function pointer reference, we open-code the check for the following: ~~~ pointer = (pointer & 1) ? *(void **)(pointer & ~1) : pointer; ~~~ Thanks to @DougGregor for the discussion and the suggestion for the pointer tagging. Thanks to @aschwaighofer for pointers to the code that I had missed. Also, thanks to @SeanROlszewski for the original code sample that led to the reduced test case. Fixes: SR-15399 (cherry picked from commit 68bc33fed325ceca8b97ee911f0adb4266bfc7bb) 12 November 2021, 01:14:12 UTC
9a5bb49 Mishal Shah 10 November 2021, 18:12:54 UTC Merge pull request #40123 from apple/shahmishal/update-swift-format-version Update the branch for swift-format to swift-5.5-branch 10 November 2021, 18:12:54 UTC
030fc01 Mishal Shah 10 November 2021, 17:33:23 UTC Update the branch for swift-format to swift-5.5-branch 10 November 2021, 17:33:23 UTC
ffcbdc6 Evan Wilde 03 November 2021, 17:42:03 UTC Make it LinkOnceODRLinkage Make the little variable LinkOnceODRLinkage so that it doesn't take up as much space. 04 November 2021, 17:03:13 UTC
7af551c Evan Wilde 03 November 2021, 17:20:59 UTC Fixing the strong imported async frame pointer flags The weakly-imported symbol was getting optimized out, then put back in as a strongly-imported symbol. This is no good. The symbol is a declaration though, so it can't be "used" directly. Instead, we assign it to another global and "use" it. That avoids the optimizations and should be fine. Even if that symbol is a nullptr because it doesn't exist, we are taking the pointer to it, which should be fine for all situations. 04 November 2021, 17:03:12 UTC
c39901d nate-chandler 03 November 2021, 21:56:29 UTC [SILGen] Handled foreign funcs with async, error, and more. (#39960) In 1ae317dd88b572e70480798bec38f60e3c485b97, all the machinery was added to enable calling ObjC functions that have both async and error conventions. The handling that was added for matching up arguments and parameters, however, failed to handle functions that had both foreign async and foreign error and other arguments. Here, that handling is fixed. The fix is in four parts: - Reverting to a single call to CallSite::emit to emit the formal params. At this point, the foreign async and/or error params will be claimed as well. - Separately counting the async and error parameters in ParamLowering::claimParams to ensure we get the right parameter slices. - Letting ArgEmitter::maybeEmitForeignArgument look for an error parameter even if it already found an async parameter. - Letting ArgEmitter::maybeEmitForeignArgument keep looking for foreign arguments after it finds one. rdar://80704984 03 November 2021, 21:56:29 UTC
61ad514 Doug Gregor 03 November 2021, 05:57:01 UTC Merge pull request #40008 from DougGregor/back-deploy-concurrency-weak-5.5 Always weak-link symbols from the concurrency library when back-deploying 03 November 2021, 05:57:01 UTC
e3d5a72 Doug Gregor 03 November 2021, 05:54:44 UTC Merge pull request #40026 from DougGregor/swift-stdlib-tool-add-support-for-back-deployed-concurrency-5.5 03 November 2021, 05:54:44 UTC
d8e594c Keith Smiley 01 November 2021, 17:59:32 UTC Use component prefix to add instead of specifics 02 November 2021, 23:24:15 UTC
aefc18d Keith Smiley 01 November 2021, 04:33:23 UTC [swift-stdlib-tool] Add support for back deployed concurrency This tool was mostly already compatible with copying `libswift_Concurrency.dylib` based on whether or not the executables it was scanning linked it. The only thing missing was that it can now end up copying from different source directories, the older `swift-5.0` directory, and the new `swift-5.5` directory. This change allows users to pass `--source-libraries` multiple times (or picks a default with both) in order to have it scan both directories for any libraries the app links. The biggest part of this change is instead of storing just the library name throughout this logic we now store the actual discovered path, so that we don't have to loop through all potential source directories each time we need to find the library, only the first time. 02 November 2021, 23:24:15 UTC
e944604 Doug Gregor 01 November 2021, 23:51:04 UTC Always weak-link symbols from the concurrency library when back-deploying This allows applications that back-deploy but only use concurrency in newer code to load and execute properly, even when the concurrency library is not available. Fixes rdar://84877644. 01 November 2021, 23:53:53 UTC
76f61e6 eeckstein 29 October 2021, 16:14:59 UTC Merge pull request #39946 from eeckstein/fix-constant-folding-5.5 [5.5] ConstantFolding: remove a wrong peephole optimization for signed "< 0" and ">= 0" comparisons 29 October 2021, 16:14:59 UTC
31b86f1 Erik Eckstein 27 October 2021, 12:20:19 UTC ConstantFolding: remove a wrong peephole optimization for signed "< 0" and ">= 0" comparisons The wrong optimization was: fold x < 0 into false, if x is known to be a result of an unsigned operation with overflow checks enabled. It was done under the wrong assumption that the result of an overflow-checked unsigned operation fits into a signed integer and is positive. This is wrong, because the result of an unsigned operation can be larger than Int.max and therefore, when used in a signed integer operation, be re-interpreted as a negative signed value. Fixes a miscompile which resulted in a missing abort on arithmetic overflow. rdar://73596890 28 October 2021, 07:14:52 UTC
21421b4 Doug Gregor 27 October 2021, 22:34:39 UTC Merge pull request #39936 from DougGregor/watchos-noasyncframepointer-backdeploy-5.5 Disable the definition and use of swift_async_extendedFramePointerFlags on watchOS 27 October 2021, 22:34:39 UTC
f65ef8d Doug Gregor 27 October 2021, 18:57:24 UTC Define `swift_async_extendedFramePointerFlags` for the watchOS simulator 27 October 2021, 19:00:07 UTC
2512478 Doug Gregor 27 October 2021, 16:48:03 UTC Rework the watchOS concurrency back-deployment async frame pointer. Introduce a few changes to the logic for watchOS concurrency back-deployment with respect to the async frame pointer. * Only apply the change to watchOS device targets, not simulator targets * Only introduce the override when no specific `-swift-async-frame-pointer=<value>` option is provided on the command line * Only override the default when deploying to watchOS < 8, and * Use "never" for the default rather than "always". This represents a different but safer trade-off than before. Setting the async bit in the frame pointer can cause older APIs (such as backtrace APIs in the OS) to crash when they encounter such frame pointers. So, with this change we never set the bit when back-deploying for watchOS device, to avoid said crashes. The trade-off here is that a back-deployed watchOS app will never have the async frame pointer bit set, so async backtraces will be unavailable even when running on watchOS 8 or newer. 27 October 2021, 16:48:03 UTC
4f6c023 Doug Gregor 27 October 2021, 15:57:15 UTC Merge pull request #39934 from DougGregor/back-deploy-fix-bundle-identifier-5.5 Fix embedded plist of back-deployed concurrency library 27 October 2021, 15:57:15 UTC
2191f87 Doug Gregor 27 October 2021, 05:24:12 UTC Disable the definition and use of swift_async_extendedFramePointerFlags on watchOS The asm definition of `swift_async_extendedFramePointerFlags` prevents the use of bitcode with the back-deployment libraries, so remove the definition and use of this symbol from watchOS binaries entirely. Instead, always force the async frame bit to be set. This trades off backtraces on older OS's for debuggability of newer ones. If it causes problems, it can be disabled via the option `-swift-async-frame-pointer=never`. Fixes rdar://84687579. 27 October 2021, 05:27:48 UTC
7f0a58f Doug Gregor 27 October 2021, 05:17:53 UTC Fix infernal Python linter warnings 27 October 2021, 05:17:53 UTC
b082f29 Doug Gregor 27 October 2021, 03:58:06 UTC Propagate Swift version information to the back-deployed binaries 27 October 2021, 04:00:53 UTC
89ca697 Doug Gregor 27 October 2021, 03:57:19 UTC Remove underscores from CFBundleIdentifier of libraries. Underscores aren't permitted in these identifiers. Fixes rdar://84645973. 27 October 2021, 04:00:53 UTC
2a460ca 冀卓疌 22 October 2021, 13:12:05 UTC support Xcode 13.0 and 13.1 RC 1 (cherry picked from commit 9f0b6436c0c3f1aae337307f17e5fd4df90592e2) 25 October 2021, 16:44:08 UTC
c088304 Doug Gregor 23 October 2021, 03:17:59 UTC Merge pull request #39876 from DougGregor/mainactor-run-hop-back-5.5 23 October 2021, 03:17:59 UTC
f53226a Doug Gregor 22 October 2021, 21:44:31 UTC Fix resilience of global actor hops and test MainActor.run. 22 October 2021, 21:44:31 UTC
6a355ae Doug Gregor 22 October 2021, 19:13:38 UTC Merge pull request #39812 from DougGregor/marker-protocol-runtime-type-metadata-5.5 Don't emit marker protocols into runtime type metadata. 22 October 2021, 19:13:38 UTC
e61f8f1 Doug Gregor 22 October 2021, 19:13:23 UTC Merge pull request #39841 from DougGregor/isolated-params-serialization-5.5 Properly serialize 'isolated' bit on function parameter declarations. 22 October 2021, 19:13:23 UTC
dd3f702 Artem Chikin 22 October 2021, 17:35:31 UTC Merge pull request #39857 from artemcm/55UpdateConcurrencyBackdeployLinkingRequireCatalyst [5.5] Update `test/Concurrency/Backdeploy/linking.swift` to require macCatalyst supported environment 22 October 2021, 17:35:31 UTC
f307d20 Doug Gregor 22 October 2021, 06:26:02 UTC Ensure that we hop off the main actor after MainActor.run. Asynchronous functions isolated to global actors hop to the global at the beginning of the function but do not hop back on return. For `MainActor.run`, this means that we would not "hop back" off the main actor after executing the closure, which lead to too much code running on the main thread. Dropping the "async" ensures that we hop back. While we my also want the general "hop back" semantics for asynchronous actor-isolated functions, for now this addresses the problem with `MainActor.run`. Fixes rdar://82138050. 22 October 2021, 15:56:51 UTC
def59df Doug Gregor 22 October 2021, 15:41:19 UTC Merge pull request #39308 from aschwaighofer/swift_async_function_pointer_kind_auto_default_5.5 [release/5.5] Revert "Default to SwiftAsyncFramePointerKind::Always for now" 22 October 2021, 15:41:19 UTC
968f1be Xi Ge 22 October 2021, 05:20:20 UTC ABI Checker: include mangled names in ABI descriptor files (#39860) Previously, we use USR as a delegate for mangled name. However, USR won't incorporate name changes made by attributes like @_silgen_name. Instead, we should add a dedicated field for canonical mangled names. rdar://84202064 22 October 2021, 05:20:20 UTC
8877d45 Artem Chikin 21 October 2021, 19:22:25 UTC Update `test/Concurrency/Backdeploy/linking.swift` to require macCatalyst supported environment Resolves rdar://84441879 21 October 2021, 19:24:45 UTC
3a95105 John McCall 20 October 2021, 23:19:37 UTC Merge pull request #39830 from rjmccall/fix-alignment-future-fragment-5.5 [5.5] Fix the alignment of future fragments for highly-aligned result types 20 October 2021, 23:19:37 UTC
4de006c Doug Gregor 20 October 2021, 17:00:13 UTC Properly serialize 'isolated' bit on function parameter declarations. Fixes rdar://83380879. (cherry picked from commit 8dbfb04aed673e1019b546e40f19d300be8e261d) 20 October 2021, 20:11:08 UTC
242bc47 Doug Gregor 20 October 2021, 18:45:42 UTC Merge pull request #39769 from nkcsgexi/84278884-5.5 [5.5] ABI checker: downgrade missing @available attributes to warnings. 20 October 2021, 18:45:42 UTC
4e96d0c Doug Gregor 20 October 2021, 18:26:44 UTC Merge pull request #39717 from nkcsgexi/83450549-5.5 20 October 2021, 18:26:44 UTC
fd1bb03 John McCall 20 October 2021, 06:07:48 UTC Better comments, fix a calculation. 20 October 2021, 17:12:04 UTC
d3d34ae Arnold Schwaighofer 19 October 2021, 23:48:38 UTC Make sure that the future fragment's storage pointer is properly aligned 20 October 2021, 06:14:32 UTC
33b5a48 Xi Ge 20 October 2021, 03:00:57 UTC Merge pull request #39815 from nkcsgexi/84425205-5.5 [5.5]Sema: allow @_originallyDefinedIn to specify identical version numbers as @available. 20 October 2021, 03:00:57 UTC
80e9fe1 Konrad `ktoso` Malawski 19 October 2021, 21:52:17 UTC 🍒 5.5 [Concurrency] set queue width on all non-apple platforms, not just linux (#39765) * [Concurrency] set queue width on all non-apple platforms, not just linux * Update stdlib/public/Concurrency/GlobalExecutor.cpp Co-authored-by: Saleem Abdulrasool <compnerd@compnerd.org> * Update stdlib/public/Concurrency/GlobalExecutor.cpp Co-authored-by: Saleem Abdulrasool <compnerd@compnerd.org> Co-authored-by: Saleem Abdulrasool <compnerd@compnerd.org> 19 October 2021, 21:52:17 UTC
48fd4cc Xi Ge 19 October 2021, 19:31:44 UTC Sema: allow @_originallyDefinedIn to specify identical version numbers as @available. rdar://84425205 19 October 2021, 21:06:38 UTC
cb3fe3d Doug Gregor 19 October 2021, 17:15:49 UTC Adjust for 5.5 branch 19 October 2021, 17:15:49 UTC
59158a1 Doug Gregor 16 October 2021, 00:00:41 UTC Don't emit marker protocols into runtime type metadata. Marker protocols don't exist at runtime, drop them when mangling a type for the purposes of runtime type metadata or reflection. Fixes rdar://82314404. (cherry picked from commit 7d7ec9e7d5119125b6b5371a9b092317b25a21d3) 19 October 2021, 15:39:19 UTC
db15620 Doug Gregor 19 October 2021, 13:50:47 UTC Merge pull request #39807 from DougGregor/back-deploy-concurrency-maccatalyst-5.5 19 October 2021, 13:50:47 UTC
3836d25 Doug Gregor 19 October 2021, 03:39:40 UTC Disable linking of the concurrency compatibility library for macCatalyst It might not be there, and we don't need it for this test. 19 October 2021, 03:41:07 UTC
b1fd8c4 Doug Gregor 18 October 2021, 23:44:40 UTC Use the proper install name for back-deployed concurrency on macCatalyst. Fixes rdar://84393581. 18 October 2021, 23:49:12 UTC
350109f Michael Gottesman 15 October 2021, 22:58:21 UTC [silgen] Fix lifetime management of tuple elements so we don't leak (#39600) * Revert "[silgen] Ensure that the outer cleanup is emitted along failure paths when initializing sub-tuple patterns" This reverts commit be922b999038eae35b8aa120e1df7b11892fcf5f. By adding some extra scopes here we are triggering some broken behavior in a bunch of projects. I am going to see if I can do another fix for this. That being said in the short term, we are reverting to unblock those projects. rdar://83770295 (cherry picked from commit 49bc96dc8df3fdc523a99d1348ab3a3ce9bf1ea7) * [silgen] When initializing tuples in SILGen, first evaluate all tuple elts and then perform sub-initialization. Previsouly we were evaluating a tuple elt and then performing the relevant sub-initialization. The problem is that a sub-initialization can invoke code that could perform an early exit cleanup. So any later tuple-elements that may need to be cleaned up along such path will not have had their cleanups initialized, resulting in a leak along such paths. With this commit, we instead evaluate all of the tuple elements and only them perform the sub-initialization ensuring that any early exits clean up all of the tuple elements. rdar://83770295 (cherry picked from commit f64180870a05bac76c5ee32764d4f8cb43cce75c) 15 October 2021, 22:58:21 UTC
cec5425 Doug Gregor 15 October 2021, 22:41:38 UTC Merge pull request #39746 from DougGregor/fix-back-deploy-mangle-test-5.5 Fix FileCheck test for back-deployed concurrency. 15 October 2021, 22:41:38 UTC
0cb981e Xi Ge 15 October 2021, 05:17:30 UTC ABI checker: downgrade missing @available attributes to warnings. rdar://84278884 15 October 2021, 20:57:07 UTC
963c679 Doug Gregor 15 October 2021, 16:37:08 UTC Merge pull request #39738 from DougGregor/no-link-back-compat-incorrectly-5.5 Ensure that we link the right set of compatibility libraries on Apple OS's 15 October 2021, 16:37:08 UTC
209cda7 Doug Gregor 15 October 2021, 16:36:46 UTC Merge pull request #39757 from DougGregor/back-deployed-concurrency-disable-exclusivity-5.5 Disable runtime exclusivity checking when using back-deployed concurrency 15 October 2021, 16:36:46 UTC
1550a6b Mishal Shah 14 October 2021, 22:58:58 UTC Merge pull request #39759 from apple/neonichu-patch-2 Fix argparser version for "main" 14 October 2021, 22:58:58 UTC
c554335 Boris Bügling 14 October 2021, 22:55:07 UTC Fix argparser version for "main" 14 October 2021, 22:55:07 UTC
61d5bcd Doug Gregor 14 October 2021, 22:40:33 UTC Disable runtime exclusivity checking when using back-deployed concurrency. The back-deployed concurrency libraries and older Swift runtimes are not compatible, so turn off runtime exclusivity checking when running on older systems. Fixes rdar://84274148. 14 October 2021, 22:44:41 UTC
e21296b Doug Gregor 14 October 2021, 19:30:37 UTC Force-link the Objective-C library in the back-deployed concurrency libs. 14 October 2021, 19:33:00 UTC
9e7a02f Doug Gregor 14 October 2021, 17:32:22 UTC Merge pull request #39733 from bnbarham/cherry-84107841 Removing flaky escalation check 14 October 2021, 17:32:22 UTC
aa3b695 Doug Gregor 14 October 2021, 17:04:58 UTC Merge pull request #39742 from ktoso/pick-limit-width-linux-5.5 🍒 5.5 [Concurrency] Limit queue width with set_width SPI call on linux 14 October 2021, 17:04:58 UTC
6210f5d Doug Gregor 14 October 2021, 06:26:32 UTC Fix FileCheck test for back-deployed concurrency. Fixes rdar://83840279. (cherry picked from commit 4bf38ea9c20b0f105f907f79a7b3e971ed203001) 14 October 2021, 16:29:51 UTC
0be0924 Konrad `ktoso` Malawski 14 October 2021, 03:12:05 UTC could it be as simple as that? 14 October 2021, 12:03:50 UTC
e76aff4 Doug Gregor 14 October 2021, 06:02:11 UTC Update the OS runtime mapping for Apple OS versions. Fixes the rest of rdar://84065193, makingn sure we don't link against compatibility libraries we don't need. 14 October 2021, 06:07:40 UTC
0b4620f Doug Gregor 13 October 2021, 20:22:02 UTC We don't need concurrency compatibility library when deploying to Swift 5.5 Part of rdar://84065193. (cherry picked from commit 09a72d7353d27d659251a5c6e0216fc486e0168a) 14 October 2021, 06:07:06 UTC
58a3114 Evan Wilde 11 October 2021, 21:17:10 UTC Removing flaky escalation check I had added this clip to verify that the task priority escalation worked as I expected. There is a bit of raciness in here with the task priority and when the priority escalation occurs. As a result, this test can be flaky. 14 October 2021, 03:27:37 UTC
8386c77 Ben Barham 14 October 2021, 03:19:18 UTC Merge pull request #39731 from bnbarham/xfail-83840279 [Test] Disable Concurrency/Backdeploy/mangling.swift to unblock CI 14 October 2021, 03:19:18 UTC
c462fd5 Ben Barham 14 October 2021, 01:24:30 UTC [Test] Disable Concurrency/Backdeploy/mangling.swift to unblock CI 14 October 2021, 01:24:30 UTC
a6ea9bf Doug Gregor 14 October 2021, 01:22:24 UTC Merge pull request #39720 from DougGregor/pick-fix-task-instance-isCancelled 14 October 2021, 01:22:24 UTC
363f3cb Doug Gregor 13 October 2021, 18:44:20 UTC Drop unintended `@_transparent`. 13 October 2021, 19:00:08 UTC
back to top