Mykola Pokhylets
5ac1cba8d1
Handle versioning of the IsolatedDeinit feature
2024-12-12 16:41:02 +09:00
Mykola Pokhylets
bc80529d02
Revert "Merge pull request #77438 from swiftlang/revert-77364-mpokhylets/non-experimental-isolated-deinit"
...
This reverts commit 11781a5fd12ee2f1eb2c
2024-12-12 16:41:02 +09:00
Konrad `ktoso` Malawski
302ab1c268
add newly required // REQUIRES: swift_feature_IsolatedDeinit
2024-11-07 21:47:24 +09:00
Konrad `ktoso` Malawski
aadc67ec0e
Revert "Make IsolatedDeinit non-experimental"
2024-11-07 09:59:00 +09:00
Rintaro Ishizaki
7bac01e8ce
[Tests] Remove swift_feature_IsolatedDeinit
2024-11-05 23:58:15 -08:00
Mykola Pokhylets
c139d1b1a7
Make IsolatedDeinit non-experimental
2024-11-05 12:19:01 +01:00
Konrad `ktoso` Malawski
43839ac5fd
Merge pull request #76995 from nickolas-pohilets/mpokhylets/disable-stack-promotion
...
Disable stack promotion for classes with isolated deinit
2024-11-04 18:07:11 +09:00
Daniel Rodríguez Troitiño
ba68faaed5
[test] Mark tests that use experimental/upcoming features as such
...
Find all the usages of `--enable-experimental-feature` or
`--enable-upcoming-feature` in the tests and replace some of the
`REQUIRES: asserts` to use `REQUIRES: swift-feature-Foo` instead, which
should correctly apply to depending on the asserts/noasserts mode of the
toolchain for each feature.
Remove some comments that talked about enabling asserts since they don't
apply anymore (but I might had miss some).
All this was done with an automated script, so some formatting weirdness
might happen, but I hope I fixed most of those.
There might be some tests that were `REQUIRES: asserts` that might run
in `noasserts` toolchains now. This will normally be because their
feature went from experimental to upcoming/base and the tests were not
updated.
2024-11-02 11:46:46 -07:00
Mykola Pokhylets
cb7a8d5cfc
Disable stack promotion for classes with isolated deinit
2024-10-31 20:43:11 +01:00
Mykola Pokhylets
67ab0d7404
Implement disabling task-local values in isolated deinit
...
As requested by the LSG during the proposal review.
See https://forums.swift.org/t/accepted-with-modifications-se-0371-isolated-synchronous-deinit/74042
2024-10-28 16:15:21 +01:00
Allan Shortlidge
c02fc4724d
Tests: Remove -disable-availability-checking from many Concurrency tests.
...
Instead, use the `%target-swift-5.1-abi-triple` substitution to compile the tests
for deployment to the minimum OS versions required for use of _Concurrency APIs.
2024-10-18 16:21:51 -07:00
Mykola Pokhylets
d8694dba1c
Added temporary workaround for stack allocation optimization breaking isolated deinit tests in optimized mode
2024-10-10 21:47:58 +02:00
Konrad `ktoso` Malawski
e345665dd4
add experimental flag to 3 more tests
2024-09-22 22:58:13 +09:00
Konrad `ktoso` Malawski
a6bc0e6759
temporary -experimental flag for IsolatedDeinit
2024-09-18 12:52:37 +09:00
Konrad `ktoso` Malawski
7d1ce789ad
Revert "Revert "Isolated synchronous deinit""
2024-09-17 17:35:38 +09:00
Alex Hoppen
c5aa49ba64
Revert "Isolated synchronous deinit"
2024-09-03 18:11:26 -07:00
Mykola Pokhylets
e9173ff2f4
Make sure legacy executor checking mode is always used in swift_task_deinitOnExecutor()
2024-07-11 13:09:08 +02:00
Mykola Pokhylets
4d0b624866
Make deinit non-isolated by default
...
Failing: Distributed/Runtime/distributed_actor_deinit.swift
2024-07-11 13:09:08 +02:00
Mykola Pokhylets
9dcea15d21
Fixed tests on Linux, Windows and older MacOS versions
2024-07-11 13:09:07 +02:00
Mykola Pokhylets
a043ebf97a
Don't switch threads when running isolated deinit of the default actor.
2024-07-11 13:09:07 +02:00
Mykola Pokhylets
411cdb7f73
Added unit-tests for (not)copying task-local values. Fixed release after deallocation.
2024-07-11 13:09:06 +02:00
