Skip to content

[4.0] IRGen: Fix test case only on x86-64 do we use indirect byval passing #11036

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

Conversation

aschwaighofer
Copy link
Contributor

@aschwaighofer aschwaighofer commented Jul 18, 2017

• Explanation: In the fix for rdar://33242303 / #10932 I added a test case that only succeeds on x86_64 platforms because it checks for the alignment of indirect byval parameters which we don’t emit on arm64. The test is written in a way that did not add the x86_64 target to the command line and would therefore fail on arm64.

• Scope of Issue: Failing test case because the test case is not narrow enough

• Origination: Recently introduced

• Risk: Low. This is a fix to a test case.

• Testing: The test case was fixed and should no longer fail during regression tests running on non x86_64 archs

rdar://33376164

@aschwaighofer
Copy link
Contributor Author

@swift-ci Please test

@aschwaighofer
Copy link
Contributor Author

@swift-ci Please test linux

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - bc6a7f0
Test requested by - @aschwaighofer

@aschwaighofer
Copy link
Contributor Author

@swift-ci Please test

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - bc6a7f0
Test requested by - @aschwaighofer

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - bc6a7f0
Test requested by - @aschwaighofer

@aschwaighofer aschwaighofer merged commit c3ff4e3 into swiftlang:swift-4.0-branch Jul 18, 2017
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.

2 participants