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

Backports 1.5.1 #36899

Merged
merged 28 commits into from
Aug 19, 2020
Merged

Backports 1.5.1 #36899

merged 28 commits into from
Aug 19, 2020

Conversation

KristofferC
Copy link
Member

@KristofferC KristofferC commented Aug 3, 2020

Backported PRs:

Non-merged PRs with backport label:

cmcaine and others added 2 commits August 3, 2020 21:57
Related to #35526. Thanks to @kimikage for the heads up.

(cherry picked from commit 6e7bc68)
@KristofferC KristofferC changed the title WIP: Backports release 1.5 WIP: Backports 1.5.1 Aug 3, 2020
@quinnj
Copy link
Member

quinnj commented Aug 3, 2020

Can we add #36819 as a backport?

@KristofferC
Copy link
Member Author

Sure, done.

@IanButterworth
Copy link
Member

Backport for the arm cpu feature detection would be good too #36485

@musm
Copy link
Contributor

musm commented Aug 4, 2020

Are PRs like #36756 + #36598 eligible for backporting?

@KristofferC
Copy link
Member Author

Upgrading libuv seems a bit too big for a patch release, in my opinion.

@jmkuhn
Copy link
Contributor

jmkuhn commented Aug 5, 2020

Could you add #36705 to enable building on ARMv7l?

@KristofferC KristofferC added release Release management and versioning. and removed backport 1.5 labels Aug 10, 2020
@non-Jedi
Copy link
Contributor

Not sure exactly what the backport policy is but #36697 would be helpful to fix #36943.

@IanButterworth
Copy link
Member

Probably a good idea to backport the documentation footer for SEO/tiobe etc. #36983

@JeffBezanson
Copy link
Member

Looks like we cannot use e438d0e, since it calls parseatom that doesn't exist in 1.5.

@KristofferC KristofferC force-pushed the backports-release-1.5 branch from fbac504 to 317b2cf Compare August 14, 2020 20:35
@KristofferC
Copy link
Member Author

Looks like we cannot use e438d0e, since it calls parseatom that doesn't exist in 1.5.

image

@KristofferC
Copy link
Member Author

@nanosoldier runbenchmarks(ALL, vs = ":release-1.5")

@KristofferC
Copy link
Member Author

@nanosoldier runtests(ALL, vs = ":release-1.5")

@nanosoldier
Copy link
Collaborator

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

@nanosoldier
Copy link
Collaborator

Your package evaluation job has completed - possible new issues were detected. A full report can be found here. cc @maleadt

@KristofferC
Copy link
Member Author

@nanosoldier runtests(["ARCHModels", "Autologistic", "BitFloats", "Dagger", "DataDrivenDiffEq", "IncrementalInference", "KissMCMC", "LiveServer", "NeuralArithmetic", "SparseGaussianProcesses", "XPORTA"], vs = ":release-1.5")

@KristofferC
Copy link
Member Author

Dropping #36856 since it changes exception types.

@KristofferC KristofferC force-pushed the backports-release-1.5 branch from 317b2cf to dea950e Compare August 18, 2020 16:35
@nanosoldier
Copy link
Collaborator

Your package evaluation job has completed - possible new issues were detected. A full report can be found here. cc @maleadt

sostock and others added 4 commits August 19, 2020 14:00
(cherry picked from commit 4d215e4)
* Deprecated features
* Comments
* Update dependency and processor feature set

(cherry picked from commit 9f83eaf)
(cherry picked from commit 9ad9daa)
yuyichao and others added 22 commits August 19, 2020 14:00
(cherry picked from commit 87c609a)
When several Julia processes compile the same package concurrently
(e.g. during a cluster run), they can conflict on the compile cache
file. This change makes a Julia process create a compile cache in a
temporary file and atomically rename it to the final cache file.

Co-authored-by: Takafumi Arakaki <tkf@@users.noreply.github.com>
(cherry picked from commit 3bbb582)
…ecache (#36638)

This seems to be  affecting Windows systems in particular

(cherry picked from commit 353e129)
This was really just a regression when switching from grisu -> ryu
algorithm for float printing. The fix is just putting [@vtjnash's
code](5d2a0ec#diff-22819a3d47074bbe6530dfef9c94969cR75)
for the grisu fix into the ryu branch.

(cherry picked from commit ada82ac)
The code was using two different `std::pair` types to pass this info around
as remnant of an earlier version and the auto conversion between the two types
does not retain the meaning we want...

Use a custom struct to hold the info to guard against this kind of errors in the future.

(cherry picked from commit 2d3288e)
* Clean up old LLVM version check
* Clean up old cores that'll probably not be used (and some that are removed from LLVM)
* Add document about data sources
* Update AArch64 feature list to match changes to the LLVM ones
* ARMv8.4 - ARMv8.6 support
* Add all known cores that I can find and all information I can find about them
* Remove a few A64 only cores from AArch32 CPU list
* Rename Apple cores (following LLVM)
* SVE register size

Co-authored-by: Ian <[email protected]>
(cherry picked from commit e0e3825)
* Missing feature from Apple A13
* Enable Cortex-A78 and Cortex-X1 on LLVM 11

    llvm/llvm-project@954db63
    https://reviews.llvm.org/D83206

* More relaxed Zen detection: treat all family 23 as Zen* and treat all model >= 0x30 as Zen2.

    GCC uses a similar fallback structure albeit based on feature.
    This should still generate **correct** code since that is always controlled by
    available features. It should be as good a scheduling model estimate as anything else.

    Fix #36826

(cherry picked from commit cd3fb4d)
We might print ANSI color codes around ERROR now, making this test unreliable.

(cherry picked from commit 537664f)
This is an LLVM bug. See upstream discussion at https://reviews.llvm.org/D85499.

(cherry picked from commit 91d384c)
Includes build fixes to ensure it is built thread-safe. Fixes #35796 regression.

(cherry picked from commit 193b21b)
This allows LLVM codegen passes to insert `inttoptr` and `ptrtoint` as it wish,
and avoids hitting any illegal ones in those passes.

Fix #36062

(cherry picked from commit 235784a)
(cherry picked from commit 00f2133)
…e vectors out of the loops in order to get a speedup in some cases where type inference otherwise takes tuple types. (#36975)

(cherry picked from commit 54d73a8)
Co-authored-by: Ian <[email protected]>
Co-authored-by: Fredrik Ekre <[email protected]>
(cherry picked from commit 5be3a54)
Not sure why this was first linked statically, as the commit that
introduced this simply had the message "restoring stuff that seems to
have been clobbered by the revert of the unintended merge to master".

Nearly all other libraries that we use are linked dynamically.

(cherry picked from commit 9267bbf)
…signed Julia (#37069)

Without this entitlement, users that wish to attach a debugger to the
codesign Julia executable they receive from `julialang.org` must strip
the codesigning signature from the Julia executable (e.g. via `codesign
--remove-signature Julia-1.5.app/Contents/Resources/bin/julia`).  This
has its disadvantages, of course, so much better to simply declare to
the OS that it's alright for other processes to attach to this process.

(cherry picked from commit bf8a8e8)
@KristofferC KristofferC force-pushed the backports-release-1.5 branch from 04d7574 to a197786 Compare August 19, 2020 12:01
@KristofferC KristofferC changed the title WIP: Backports 1.5.1 Backports 1.5.1 Aug 19, 2020
@KristofferC
Copy link
Member Author

Should be good to go now.

@KristofferC KristofferC merged commit 21e0f04 into release-1.5 Aug 19, 2020
@KristofferC KristofferC deleted the backports-release-1.5 branch August 19, 2020 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Release management and versioning.
Projects
None yet
Development

Successfully merging this pull request may close these issues.