Skip to content
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

[Stdlib][ABI] Resolve ABI FIXME #25 #6246

Merged
merged 1 commit into from
Dec 14, 2016

Conversation

CodaFi
Copy link
Contributor

@CodaFi CodaFi commented Dec 13, 2016

I introduced this in #3108 because we no longer require this SPI.

Resolves rdar://problem/19696522

// CHECK-NOT: .loc
// CHECK: .loc {{[0-9]}} 6 {{[0-9]}}
// CHECK: .loc {{[0-9]}} 6 {{[0-9]}} prologue_end
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@adrian-prantl This change seems sketchy to me.

Copy link
Member

Choose a reason for hiding this comment

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

Interestingly enough, this is something that I was recently looking at. Something has changed and when building swift against upstream-with-swift on clang/LLVM, it seems that the prolgue_end marker is no longer emitted. The MF does see the FrameSetup markers on the prologue instructions, but when the line record is constructued, we ignore the FrameSetup MIFlag and just drop the prologue tracking on the floor.

Also, it seems that for some reason this test is marked as XFAIL on Linux. Why is that?

Copy link
Contributor

Choose a reason for hiding this comment

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

Judging from the version control history, this testcase was XFAILed some time during the Linux bringup and hasn't been looked at since.

@compnerd: could you file bugs for both of these issues and CC/assign it to me?

@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 13, 2016

@swift-ci please test.

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - f68848bfd6d4e967bad1ad365c12f2194c6c1e08
Test requested by - @CodaFi

@slavapestov
Copy link
Contributor

This should address the build failure: #6247

@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 13, 2016

Thanks @slavapestov. I'll take this opportunity to do what I promised in July and write a real doc comment for @jrose-apple

@slavapestov
Copy link
Contributor

Let us know when/if you want that radar closed :)

Process arguments are now fetched per-platform
@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 13, 2016

@swift-ci please smoke test.

@jrose-apple
Copy link
Contributor

IIRC we still needed _didEnterMain because of interpreter mode. Or do we use the override entry point for that now?

@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 13, 2016

Immediate got patched to use the new SPI in #3108. Everything goes through the overrides in the stubs.

@jrose-apple
Copy link
Contributor

All right then. Thanks, @CodaFi!

@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 14, 2016

⛵️

@CodaFi CodaFi merged commit be9f205 into swiftlang:master Dec 14, 2016
@CodaFi CodaFi deleted the the-farmer-refuted branch December 14, 2016 17:20
@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 14, 2016

@slavapestov You can close the radar now!

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.

6 participants