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

gf: fix jl_isa_compileable_sig again #30458

Merged
merged 1 commit into from
Jan 3, 2019
Merged

Conversation

vtjnash
Copy link
Member

@vtjnash vtjnash commented Dec 20, 2018

The last attempts were pretty good, but still missed a lot.
But this is what you find when you actually try to test it.
This is not too important, but it can reduce compilation
performance in some case, so it is not ideal.

@vtjnash vtjnash added bugfix This change fixes an existing bug needs nanosoldier run This PR should have benchmarks run on it backport pending 1.0 labels Dec 20, 2018
@vtjnash
Copy link
Member Author

vtjnash commented Dec 20, 2018

@nanosoldier runbenchmarks(ALL, vs = ":master")

@nanosoldier
Copy link
Collaborator

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

This was referenced Dec 27, 2018
The last attempts were pretty good, but still missed a lot.
But this is what you find when you actually try to test it.
This is not too important, but it can reduce compilation
performance in some case, so it is not ideal.
@vtjnash vtjnash force-pushed the jn/isa_compileable_sig_again branch from aacc36f to 0cae91a Compare January 2, 2019 20:30
@vtjnash vtjnash added backport pending 1.1.1 and removed backport pending 1.1 needs nanosoldier run This PR should have benchmarks run on it labels Jan 2, 2019
@vtjnash vtjnash merged commit 76e7421 into master Jan 3, 2019
@vtjnash vtjnash deleted the jn/isa_compileable_sig_again branch January 3, 2019 18:15
KristofferC pushed a commit that referenced this pull request Jan 11, 2019
The last attempts were pretty good, but still missed a lot.
But this is what you find when you actually try to test it.
This is not too important, but it can reduce compilation
performance in some case, so it is not ideal.

(cherry picked from commit 76e7421)
@StefanKarpinski StefanKarpinski added backport 1.1 triage This should be discussed on a triage call and removed triage This should be discussed on a triage call backport 1.0 labels Jan 31, 2019
@StefanKarpinski StefanKarpinski added the triage This should be discussed on a triage call label Jan 31, 2019
@JeffBezanson JeffBezanson removed backport 1.0 triage This should be discussed on a triage call labels Jan 31, 2019
@Keno Keno mentioned this pull request Mar 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix This change fixes an existing bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants