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

assume getfield is non-volatile if inferred to be constant #18058

Merged
merged 1 commit into from
Aug 17, 2016

Conversation

JeffBezanson
Copy link
Sponsor Member

Hopefully fixes regression caused by #18017.

@JeffBezanson
Copy link
Sponsor Member Author

@nanosoldier runbenchmarks(ALL, vs="@b80dad40ab36bcd7e11859d36b51c6afcf008148")

@KristofferC
Copy link
Sponsor Member

@nanosoldier runbenchmarks(ALL, vs="@b80dad4")

@vtjnash
Copy link
Sponsor Member

vtjnash commented Aug 16, 2016

lgtm. could we test with something like checking if the following folds down to jlapi 2?

type A; x::Void; end
f(a::A) = a.x

why did this cause such performance issues?

@JeffBezanson
Copy link
Sponsor Member Author

I believe the big regression was due to the getfield calls in Core.Inference.return_type not being removed, in turn causing promote_op not to be constant-folded.

@tkelman tkelman added the kind:potential benchmark Could make a good benchmark in BaseBenchmarks label Aug 16, 2016
@JeffBezanson
Copy link
Sponsor Member Author

32-bit AV timeout?

@nanosoldier
Copy link
Collaborator

Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels

@vtjnash
Copy link
Sponsor Member

vtjnash commented Aug 16, 2016

looks like it fixed most of them, but all the sumelt are still regressed

@JeffBezanson
Copy link
Sponsor Member Author

It's possible that's a different issue. In my bisect I only looked at nbody_vec since it was the worst regression by a large margin.

@JeffBezanson JeffBezanson merged commit 8d37d65 into master Aug 17, 2016
@tkelman tkelman deleted the jb/18017 branch August 17, 2016 22:29
tkelman pushed a commit that referenced this pull request Aug 20, 2016
fixes regression caused by #18017

(cherry picked from commit e35a7f6)
ref #18058
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:potential benchmark Could make a good benchmark in BaseBenchmarks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants