Backports for 1.8-rc2/1.8.0 #45491
Backports for 1.8-rc2/1.8.0 #45491
Conversation
(cherry picked from commit a5438f9)
This new build doesn't depend on Kerberos Co-authored-by: Mosè Giordano <[email protected]> (cherry picked from commit 28d9326)
|
JuliaLang/Pkg.jl#2990 should be included. This fixes a very annoying bug which is still present in 1.8.0-rc1 |
|
Yep, thanks for the pointer. |
|
Eh, that commit is already included from what I can see. So could you elaborate a bit on what the issue is? |
|
See: When running "test" in package manager I get the message: Which is this bug: JuliaLang/Pkg.jl#2989 which is closed, but still present in 1.8.0-rc1 |
|
@nanosoldier |
|
@nanosoldier |
|
Something went wrong when running your job: Unfortunately, the logs could not be uploaded. |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. |
…5615) `is_foldable` should be more aligned with `Base.@assume_effects`. This should be backported to 1.8 also.
|
@nanosoldier |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. |
|
@nanosoldier |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. |
|
@nanosoldier |
|
Should have been run with assertions: @nanosoldier |
This fixes hundreds of invalidations from Unitful. Co-authored by: Shuhei Kadowaki <[email protected]>
`@time` now shows if any of the compilation time was spent recompiling invalidated methods. The new percentage is % of the compilation time, not the total execution time. (cherry picked from commit 7074f04)
(cherry picked from commit 9320fba)
This is theoretically okay, but unlikely to be intended ever. (cherry picked from commit d81724a)
Ensures we do not get easily wedged into bad states. (cherry picked from commit d0e28af)
(cherry picked from commit b49a1b4)
(cherry picked from commit 4f1c68e)
(cherry picked from commit 9b83dd8)
This prevents a compiler warning on some systems (cherry picked from commit 05eb153)
KristofferC
force-pushed
the
backports-release-1.8
branch
from
a87550d
to
2b6c746
Compare
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. |
|
Your package evaluation job has completed - possible new issues were detected. A full report can be found here. |
* Bug fix for `max_collect_interval` computation (#45727) Currently constrained to `totalmem / ncores / 2` for `_P64` which results in a very short collect interval when you're running with a smaller number of threads on a machine with many cores. Changes this to `totalmem / nthreads / 2` which, for two of our tests, resulted in 40% and 60% runtime reduction (!!) as well as GC time reduction from 46% to 10% and 64% to 11%. * Move GC init after threading init To allow use of `jl_n_threads` in GC initialization.
Backported PRs:
isdispatchtupleconsistent fortypeof(Union{})#45348pkgorigins#44318Diagonal*OffsetMatrix#45548threadshere is wrong to usenthreads#45547is_concrete_eval_eligibleutility query tois_foldable#45615@assume_effects#45625@assume_effectsdocs #45675run#45710max_collect_intervalcomputation #45727Contains multiple commits, manual intervention needed:
reverse!#45871Non-merged PRs with backport label:
@threadsloop exit #45899BLAS.[sy/he]mm!#45605invoked fallbacks #45001stridesforReshapedArraywith strided parent. #44507