Skip to content

Conversation

gottesmm
Copy link
Contributor

@gottesmm gottesmm commented Apr 2, 2018

…ing stubs.

This is only necessary on x86-64. On arm/arm64 we are already ok since the
assembly marker that we use there does not suffer from this issue.

For x86-64 we need to solve the problem upstream by not tailing calling
objc_retainAutoreleasedReturnValue.

rdar://38675842

…ing stubs.

This is only necessary on x86-64. On arm/arm64 we are already ok since the
assembly marker that we use there does not suffer from this issue.

For x86-64 we need to solve the problem upstream by not tailing calling
objc_retainAutoreleasedReturnValue.

rdar://38675842
@gottesmm
Copy link
Contributor Author

gottesmm commented Apr 2, 2018

@swift-ci test and merge

@jrose-apple jrose-apple requested a review from gparker42 April 2, 2018 18:35
@gottesmm gottesmm merged commit 9accf4a into swiftlang:master Apr 2, 2018
@gottesmm gottesmm deleted the pr-2aa38499b4210d8c66240446893c4f340fc62351 branch April 2, 2018 20:30
@gparker42
Copy link
Contributor

Where is the bug report for fixing x86_64's incorrect tail call to objc_retainAutoreleasedReturnValue? That sounds like a bug in clang.

@gottesmm
Copy link
Contributor Author

gottesmm commented Apr 2, 2018

It is a bug in clang. There is a radar for it: rdar://38675842. I am in the process of fixing it. But that doesn't mean that in the mean time we shouldn't do the right thing for other platforms.

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