Skip to content

[SR-13571] build release and debug variants of swiftrt.obj, swiftCore #70230

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 57 commits into from
Closed

Conversation

devKobe24
Copy link

@devKobe24 devKobe24 commented Dec 5, 2023

Modify to build both debug and release variants, providing the runtime as swiftCore.dll and swiftCored.dll, and enable building with both /MD and /MDd to activate debug builds.

Issue: [SR-13571]

devKobe24 and others added 30 commits November 15, 2023 19:54
I restored the code to its original state in 'test/stdlib/UnsafePointerDiagnostics.swift
Issue: [SR-6360]
Tag: #48910

We could make things easier on people by adding an unavailable typealias with a renamed field.

Resolve: #48910, fix: #69881

cc: @glessard
Issue: [[SR-6360](https://bugs.swift.org/browse/SR-6360)]
Tag: #48910

We could make things easier on people by adding an unavailable typealias with a renamed field.

Resolve: #48910, fix: #69881
Issue:[SR-6360]
Tag: #48910

Modified: stdlib/public/core/UnsafeRawBufferPointer.swift.gyb

Resolve: #48910, fix: #69909
Issue: [SR-6360]
Tag: #48910

Modified: stdlib/public/core/UnsafeRawBufferPointer.swift

Resolve: #48910, fix: #69909
[stdlib]Catch the reasonable mistake 'UnsafeRawMutableBufferPointer'
- Modified: stdlib/public/core/UnsafeRawBufferPointer.swift
…state.

- Modified: swift/stdlib/public/core/UnsafeRawBufferPointer.swift.gyb
- Modified: swift/test/stdlib/UnsafePointerDiagnostics.swift
[stdlib]Catch the reasonable mistake 'UnsafeRawMutableBufferPointer'
- Modified: stdlib/public/core/UnsafeRawBufferPointer.swift
- Modified: swift/test/stdlib/UnsafePointerDiagnostics.swift
[stdlib]Catch the reasonable mistake 'UnsafeRawMutableBufferPointer'
- Modified: swift/test/stdlib/UnsafePointerDiagnostics.swift
- Modified: swift/test/stdlib/UnsafePointerDiagnostics.swift
Previously the branches of a ternary would cut off
the coverage after a throwing expression, since
they have their own region, and we pop child
regions when leaving. Update the logic to use the
existing counter adjustment logic when we leave
the scope, ensuring that we push a new counter to
reflect the exit count of the scope.
Ensure that `try?` expressions appropriately
scope the regions generated by child
error-throwing expressions, such that the
non-error branch does not extend beyond the region
of the `try?`.
Previously we would ignore the effect that an if
statement or ternary's condition exit counter might
have on its branches, as we assumed a condition
can't do any control flow. However, in the case
where the condition throws an error, we need to
account for the error branch.
NuriAmari and others added 27 commits November 28, 2023 13:36
…ture

Prviously swift-ide-test enabled importing of ObjC forward declarations
with the -enable-objc-forward-declarations option. The compiler enables
the same behavior via -enable-upcoming-feature.

Now that swift-ide-test also supports upcoming-features, make enabling
the ImportObjcForwardDeclarations language feature have the expected
effect in swift-ide-test.

The old flag is also removed.
…nitializers

should be nonisolated if all initialized properties are Sendable with nonisolated
default values.
Values produced by address-only `enum` instructions have non-none
ownership.  And because `enum` is representation-changing, they have
`owned` ownership.

This corresponds at the opaque values SIL stage to the fact that at the
address-lowered SIL stage the storage location has non-trivial
initialization which must be `destroy_addr`d, regardless of whether an
empty case was stored to it.
… marked as invalid

Capability couldn't be determined for expressions like that which
means that inference should be delayed until root becomes available.

Resolves: #69936
…tributes

ClangImporter converts NS_SWIFT_SENDABLE into `SynthesizedProtocolAttr`
which needs to be recognized by the request that collects all of the
protocols that the given protocol inherits.
… for synthesized protocols

ClangImporter adds `SynthesizedProtocolAttr` to model inheritance
from `Sendable` on protocols imported from Objective-C.
…edNominalTypeDecls`

Some places use `getDirectlyInheritedNominalTypeDecls` directly
instead of fetching it through a request, so lift the check there
instead (direct use of `getDirectlyInheritedNominalTypeDecls`
could be refactored separately).
… of the embedded stdlib to cover common embedded targets
./utils/cmpcodesize/cmpcodesize/main.py:20:71: E231 missing whitespace after ','

./utils/round-trip-syntax-test:20:20: E721 do not compare types, for exact checks use `is` / `is not`, for instance checks use `isinstance()`

./utils/round-trip-syntax-test:21:16: E721 do not compare types, for exact checks use `is` / `is not`, for instance checks use `isinstance()`

I can't find any uses of round-trip-syntax-test, so I don't know if
this fix is correct.
This shouldn’t be needed anymore since we migrated code completion to be solver-based.

rdar://91403086
…ssible

The real-world use case here is the `Task` initializer in the added test case. In general, we should only prefer to insert an unapplied function reference if it has a better type relation than calling the function because, in most cases, you want to call functions and not get unapplied references to them.

rdar://90456105
This test was already passing. Probably fixed by migrating to solver-based completions.

rdar://88883761
The issue no longer occurs on `main`. Add a test case for it.

Fixes #57148
Fixes #57149
@devKobe24 devKobe24 requested a review from a team as a code owner December 5, 2023 08:49
@devKobe24 devKobe24 closed this Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants