Skip to content

[windows] Temporarily guard lifetime dependence diagnostics #74599

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

Merged
merged 1 commit into from
Jun 21, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,11 @@ private func log(prefix: Bool = true, _ message: @autoclosure () -> String) {
let lifetimeDependenceDiagnosticsPass = FunctionPass(
name: "lifetime-dependence-diagnostics")
{ (function: Function, context: FunctionPassContext) in
#if os(Windows)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we consider limiting this to os(Windows) && arch(arm64) and same throughout? Is there any thing that would be useful that we could gather to help isolate this issue?

Copy link
Contributor Author

@atrick atrick Jun 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we consider limiting this to os(Windows) && arch(arm64) and same throughout?

Not much point. These passes literally do nothing at the moment. They just process the SIL using a few SwiftCompilerSources helpers and crash if the SIL is invalid according to those helpers.

Is there any thing that would be useful that we could gather to help isolate this issue?

For the crashing function, identifying the difference in -emit-silgen between x86 and arm64 would be a good start. --Note that the pretty stack trace should print the name of the function being compiled.--
I can't imagine why there's any difference in SIL.

A symbolicated stack trace might be nice.

In general, I don't want to get any compiler crashers for projects that haven't tried to build with an asserts compiler.

But since I won't be able to look at it for a week, there's no reason to hold up any toolchain builds.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, sounds like the value of the additional SIL validation is low?

if !context.options.hasFeature(.NonescapableTypes) {
return
}
#endif
log(prefix: false, "\n--- Diagnosing lifetime dependence in \(function.name)")
log("\(function)")

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,11 @@ private func log(prefix: Bool = true, _ message: @autoclosure () -> String) {
let lifetimeDependenceInsertionPass = FunctionPass(
name: "lifetime-dependence-insertion")
{ (function: Function, context: FunctionPassContext) in
#if os(Windows)
if !context.options.hasFeature(.NonescapableTypes) {
return
}
#endif
log(prefix: false, "\n--- Inserting lifetime dependence markers in \(function.name)")

for instruction in function.instructions {
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,11 @@ private func log(prefix: Bool = true, _ message: @autoclosure () -> String) {
let lifetimeDependenceScopeFixupPass = FunctionPass(
name: "lifetime-dependence-scope-fixup")
{ (function: Function, context: FunctionPassContext) in
#if os(Windows)
if !context.options.hasFeature(.NonescapableTypes) {
return
}
#endif
log(prefix: false, "\n--- Scope fixup for lifetime dependence in \(function.name)")

let localReachabilityCache = LocalVariableReachabilityCache()
Expand Down