-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[release-0.6] backports for 0.6.0-rc2 #21878
Conversation
* clearing the meaning of comment * correct back file name. (cherry picked from commit 1571b62)
(cherry picked from commit 700bc5f)
most notably in Core.Inference, this may cause the addition of bad edges and suboptimal results (cherry picked from commit 49c1910) ref #21690 inference: improve function call signatures ensures that abstract_iteration gets better information, and that specialization can compile these methods ahead-of-time (cherry picked from commit 0250e4f)
This was caused by incorrectly using a TypeVar as the value of a static parameter in the case of a compiled specialization whose signature is not a leaf type. In this case, one slot was specialized on `Function`, but the slot with the static parameter had a leaf type. (cherry picked from commit a581292) ref #21729
(cherry picked from commit 4d08b54)
* Improve docstrings for norm, vecnorm, normalize and normalize! Add equations defining the norms, reorganize the docstrings by argument type, and mention what "normalizing" means. * Remove docstring for the norm() function (cherry picked from commit e257ef4)
(cherry picked from commit 310b6dd)
* Optimize remotecall pattern used in distributed loading (cherry picked from commit 9694de7)
(cherry picked from commit 1129de3)
Avoid a library call into GMP. (cherry picked from commit 05708f8) ref #21231 speed-up prevpow2 & nextpow2 for BigInt (cherry picked from commit 42fd2a7) GMP: add flipsign[!] functions and use more iszero/isneg/ispos (cherry picked from commit f63bdfd) add ZERO & ONE global BigInt constants for optimization (cherry picked from commit b521acd)
… calls (cherry picked from commit 66b8036) ref #21718 don't insert toplevel expression unless there are imports (cherry picked from commit 18291b0) eliminate unnecessary array allocations from isexpr and extract_imports functions (cherry picked from commit 305037a) test fixes (cherry picked from commit 24a74a5)
I guess it's too late for rc2, but would it be possible for PR #21695 to be included before 0.6 final? |
d818788 was in pretty good shape on pkgeval https://gist.github.com/df43d5af59dd34a3520e59a57c7ff3d0 with one spurious new failure in LPVSpectral, and Feather is segfaulting on this branch as opposed to freezing on rc1 (it was working up until April 6th though https://github.com/JuliaCI/pkg.julialang.org/blob/88a41b735886f267c8e71ad63be5b3e7eba38449/logs/Feather_0.6.log) But I think there have been enough new bugfixes on master that it'd be better to get them in here and re-run pkgeval again. |
@nanosoldier |
@jlbuild !nuke
|
Status of be004c1 builds:
|
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels |
ouch, what happened to date parsing? |
hm. flaky false alarm then? @nanosoldier |
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels |
https://gist.github.com/4804ae73c6d5cec89d78890617c558dc same Feather issue (#21920) and MatrixNetworks had a tolerance too tight merging and tagging this as rc2 |
@staticfloat @yuyichao can you check on and reconnect the old arm buildbot? the new buildbots aren't quite ready to be making releases off of just yet |
runbenchmarks(ALL, vs = "@6bdb3950bdf64152")
vs 0.6.0-rc1