-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
async func that is conditionally recursive crashes nightly compiler #68708
Labels
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
triage needed
This issue needs more specific labels
Comments
dnadoba
added
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
triage needed
This issue needs more specific labels
labels
Sep 22, 2023
rdar://115905828 |
aschwaighofer
added a commit
to aschwaighofer/swift
that referenced
this issue
Feb 6, 2024
github.com/swiftlang/issues/68708 rdar://115905828
This was referenced Feb 6, 2024
aschwaighofer
added a commit
to aschwaighofer/llvm-project
that referenced
this issue
Feb 7, 2024
The call to the inlining utility does not update the call graph. Leading to assertion failures when calling the utility to update the call graph. Instead rely on an inline pass to run after coro splitting and use alwaysinline annotations. github.com/swiftlang/swift/issues/68708 rdar://115905828
aschwaighofer
added a commit
to aschwaighofer/llvm-project
that referenced
this issue
Feb 7, 2024
The call to the inlining utility does not update the call graph. Leading to assertion failures when calling the utility to update the call graph. Instead rely on an inline pass to run after coro splitting and use alwaysinline annotations. github.com/swiftlang/swift/issues/68708
aschwaighofer
added a commit
to llvm/llvm-project
that referenced
this issue
Feb 7, 2024
The call to the inlining utility does not update the call graph. Leading to assertion failures when calling the call graph utility to update the call graph. Instead rely on an inline pass to run after coro splitting and use alwaysinline annotations. github.com/swiftlang/swift/issues/68708
aschwaighofer
added a commit
to aschwaighofer/llvm-project
that referenced
this issue
Apr 9, 2024
…ttailcc thunks The call to the inlining utility does not update the call graph. Leading to assertion failures when calling the call graph utility to update the call graph. Instead rely on an inline pass to run after coro splitting and use alwaysinline annotations. We can only do this if the calling convention used for the thunks is `swifttailcc` otherwise we would break clients that use other calling conventions. Previous instance of this PR was llvm#80904. github.com/swiftlang/swift/issues/68708
aschwaighofer
added a commit
to aschwaighofer/llvm-project
that referenced
this issue
Apr 16, 2024
…ttailcc thunks The call to the inlining utility does not update the call graph. Leading to assertion failures when calling the call graph utility to update the call graph. Instead rely on an inline pass to run after coro splitting and use alwaysinline annotations. We can only do this if the calling convention used for the thunks is `swifttailcc` otherwise we would break clients that use other calling conventions. Previous instance of this PR was llvm#80904. github.com/swiftlang/swift/issues/68708
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
triage needed
This issue needs more specific labels
The following program crashes 5.9 nightly and main nightly:
crash backtrace:
Reproduce:
Either compile the code snipped above or the attached Swift Package with
swift build
PlaygroundExecutbale.zip
Note: only tested in docker on Linux (swiftlang/swift:nightly-main-jammy)
Version: Swift version 5.11-dev (LLVM 5601e23279f85d8, Swift a119aaf)
also tested with: Swift version 5.9.2-dev (LLVM b3da2fc5510a8c2, Swift 49fe7f7)
The text was updated successfully, but these errors were encountered: