Skip to content

IRGen: Use clangs's LLVM datalayout #16842

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

Conversation

aschwaighofer
Copy link
Contributor

It knows better ...

rdar://40275689

It knows better ...

rdar://40275689
@aschwaighofer
Copy link
Contributor Author

@swift-ci Please test

@aschwaighofer
Copy link
Contributor Author

cc @gottesmm

@gottesmm
Copy link
Contributor

Thanks!

@aschwaighofer aschwaighofer merged commit 042d837 into swiftlang:master May 25, 2018
@@ -0,0 +1,47 @@
; RUN: %swiftc_driver_plain -frontend -target x86_64-apple-darwin10 -emit-object %s
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a specific reason to use %swiftc_driver_plain -frontend instead of %swift?

Copy link
Contributor Author

Choose a reason for hiding this comment

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


; Make sure we update the datalayout with the current clang's. clang knows
; better about the ABI intricacies.
; This test case woud crash if we did not do this because of i64:128 in the
Copy link
Contributor

Choose a reason for hiding this comment

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

s/woud/would/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

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.

4 participants