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

CI: use DEVELOPMENT-SNAPSHOT-2019-01-23-a #780

Merged
merged 2 commits into from Jan 25, 2019

Conversation

weissi
Copy link
Member

@weissi weissi commented Jan 24, 2019

Motivation:

Newer Swift versions are good and we should test them, this one threw a few curveballs at us:

Modifications

  • @inline(__always) to help the optimiser
  • update Swift version

Result:

@weissi weissi requested a review from Lukasa January 24, 2019 17:41
@weissi weissi added the patch-version-bump-only For PRs that when merged will only cause a bump of the patch version, ie. 1.0.x -> 1.0.(x+1) label Jan 24, 2019
@weissi weissi added this to the 2.0.0 milestone Jan 24, 2019
@Lukasa
Copy link
Contributor

Lukasa commented Jan 24, 2019

Woop CI failure.

@weissi
Copy link
Member Author

weissi commented Jan 24, 2019

Huh, negative amount of remaining allocations, will investigate 🤣

@weissi weissi force-pushed the jw-DEVELOPMENT-SNAPSHOT-2019-01-23-a branch from d8abe26 to 86bd77b Compare January 25, 2019 18:53
@weissi
Copy link
Member Author

weissi commented Jan 25, 2019

yaay, @Lukasa the inliner threshold must have changed, but now it finally passes 🙌

@@ -74,6 +74,9 @@ private func writeTrailers(wrapOutboundOut: (IOData) -> NIOAny, ctx: ChannelHand
}
}

// starting about swift-5.0-DEVELOPMENT-SNAPSHOT-2019-01-20-a, this doesn't get automatically inlined, which costs
// 2 extra allocations so we need to help the optimiser out.
@inline(__always)
Copy link
Member Author

Choose a reason for hiding this comment

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

@eeckstein between swift-5.0-DEVELOPMENT-SNAPSHOT-2019-01-13-a and swift-5.0-DEVELOPMENT-SNAPSHOT-2019-01-20-a this suddenly didn't get inlined anymore without any code changes.

Is that expected? It was stable from at least Swift 4.0.1 until now and then suddenly last week it broke...

Copy link
Member Author

Choose a reason for hiding this comment

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

and thanks again @aschwaighofer for apple/swift#21933 which will make debugging that sort of thing unnecessary in the future :)

@weissi weissi force-pushed the jw-DEVELOPMENT-SNAPSHOT-2019-01-23-a branch from 86bd77b to 83479ca Compare January 25, 2019 19:06
@weissi weissi merged commit 58a58b9 into apple:master Jan 25, 2019
@weissi weissi deleted the jw-DEVELOPMENT-SNAPSHOT-2019-01-23-a branch January 25, 2019 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch-version-bump-only For PRs that when merged will only cause a bump of the patch version, ie. 1.0.x -> 1.0.(x+1)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

track down extra allocation in bytebuffer_lots_of_rw track down the two extra allocations in Swift 5
2 participants