DO NOT MERGE: v1.12 branch for comparison to master #202
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nickrobinson251
force-pushed
the
v1.12.0-DEV+RAI
branch
4 times, most recently
from
966538b to
9da665d
Compare
d-netto
force-pushed
the
v1.12.0-DEV+RAI
branch
from
9da665d to
48a5871
Compare
nickrobinson251
force-pushed
the
v1.12.0-DEV+RAI
branch
from
48a5871 to
5974904
Compare
DelveCI
force-pushed
the
v1.12.0-DEV+RAI
branch
7 times, most recently
from
1cff7d7 to
1e6e20d
Compare
DelveCI
force-pushed
the
v1.12.0-DEV+RAI
branch
5 times, most recently
from
02e0f68 to
35024c5
Compare
DelveCI
force-pushed
the
v1.12.0-DEV+RAI
branch
4 times, most recently
from
fb189dc to
7e4f1cb
Compare
Reimplement all of the trim verification support in Julia as a compiler analysis pass. Move all this verification code into the Compiler julia code, where we have much better utilities for pretty printing and better observability for analysis. (cherry picked from commit 1045bd8)
Recompute some O(n) things a bit less on every statement. Fix an assert that ensured LimitedAccuracy does not accidentally get preserved when it should have been deleted: the (local) cache should not contain things that are marked as dead (RIP), as that was leading to much code not getting cached when it logically should have. Simplify the computation of frame_parent when the cycle_parent isn't needed. (cherry picked from commit 0366a2a)
- disable load path setup - remove upstreamed change to utf8proc_map - fix warning for accessing mod.main in the wrong world - remove binding backedges when trimming (cherry picked from commit d77c24f)
This updates the pin to point to main rather than a PR again, and also includes the commit: ``` b7a1c63 * Guard against assumptions that children exist ``` Fixes JuliaLang#57402 (cherry picked from commit 61de3a4)
Closes JuliaLang#46016 (cherry picked from commit b0323ab)
This change removes an inconsistency between `>:` and `<:`. We were
parsing `where {A>:B>:C}` forms, but not recognizing them in lowering.
Before:
```
julia> Vector{T} where Int<:T<:Number
Vector{T} where Int64<:T<:Number
julia> Vector{T} where Number>:T>:Int
ERROR: syntax: invalid bounds in "where" around REPL[14]:1
```
After:
```
julia> Vector{T} where Number>:T>:Int
Vector{T} where Int64<:T<:Number
```
(cherry picked from commit 2e57730)
…uliaLang#57558) Somebody may replace the type with an int. Fixes JuliaLang#57515. (cherry picked from commit bfe9c2f)
This restores 1.11 behavior. However, I find this function a bit problematic, since it is asking whether the binding is `constant` in a particular sense, but not whether it is `const` (in the sense of having been declared with the keyword or equivalent), so the shortening is confusing. However, we don't need to address that now. Fixes JuliaLang#57475. (cherry picked from commit 1ff98a5)
… to 7264a49 (JuliaLang#58527) Stdlib: LinearAlgebra URL: https://github.com/JuliaLang/LinearAlgebra.jl.git Stdlib branch: release-1.12 Julia branch: backports-release-1.12 Old commit: 4e7c3f4 New commit: 7264a49 Julia version: 1.12.0-beta3 LinearAlgebra version: 1.12.0 Bump invoked by: @jishnub Powered by: [BumpStdlibs.jl](https://github.com/JuliaLang/BumpStdlibs.jl) Diff: JuliaLang/LinearAlgebra.jl@4e7c3f4...7264a49 ``` $ git log --oneline 4e7c3f4..7264a49 7264a49 Backports release 1.12 (JuliaLang#1353) ``` Co-authored-by: jishnub <[email protected]>
…liaLang#58483) (cherry picked from commit e3982cd)
(cherry picked from commit 4d96cb4)
JuliaLang#58474) (cherry picked from commit 720d0f5)
(cherry picked from commit 053c739)
This allows constructors like `Tuple{Type{Vector{Foo}},
UndefInitializer, Tuple{Int}}` to precompile as usual
Appears to have a minimal effect on the stdlib pkgimages:
```julia
--- before.txt 2025-05-23 08:36:20.171870043 -0400
+++ after.txt 2025-05-22 14:48:49.003869097 -0400
@@ -47,7 +47,7 @@
20K ../julia/usr/share/julia/compiled/v1.13/Logging/pkgimage.so
20K ../julia/usr/share/julia/compiled/v1.13/Logging/pkgimage.so
3.5M ../julia/usr/share/julia/compiled/v1.13/Markdown/pkgimage.so
-3.5M ../julia/usr/share/julia/compiled/v1.13/Markdown/pkgimage.so
+3.6M ../julia/usr/share/julia/compiled/v1.13/Markdown/pkgimage.so
184K ../julia/usr/share/julia/compiled/v1.13/Mmap/pkgimage.so
184K ../julia/usr/share/julia/compiled/v1.13/Mmap/pkgimage.so
28K ../julia/usr/share/julia/compiled/v1.13/MozillaCACerts_jll/pkgimage.so
```
Resolves JuliaLang#58497.
(cherry picked from commit f8ece05)
…#58488) We only put debuginfo here if we ran the optimizer, so if there isn't debuginfo here, then we either didn't run the optimizer or were the result of const-prop. In the former case, we don't need to invalidate the code for instrumentation (it cannot have code from it). In the later case, we should already have an edge from the non-const-prop result. This only matters for generated functions, since otherwise we have Method's source's accurate debuginfo already and this is just a duplicate reference to it. Fix JuliaLang#58227 (cherry picked from commit d5442db)
…58542) Add missing compatibility annotation for `isdefinedglobal`. Fixes JuliaLang#58528. (cherry picked from commit 953903b)
…Lang#58261) (cherry picked from commit 58daba4)
…oncrete evaluated) (JuliaLang#58401) (cherry picked from commit 86a3e1a)
Update branch info to `release-1.12`, so that we can bump the SparseArrays.jl stdlib.
This reverts commit f15d417.
…s from packages succeed. TODO: remove this once alpha/beta is released # Conflicts: # VERSION # Conflicts: # VERSION # Conflicts: # VERSION
Prevent transparent huge pages (THP) overallocating pysical memory. Co-authored-by: Adnan Alhomssi <[email protected]>
Prepend `[signal (X) ]thread (Y) ` to each backtrace line that is displayed. Co-authored-by: Diogo Netto <[email protected]>
Also show the signal number when we have it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See also RAICode PR https://github.com/RelationalAI/raicode/pull/22602/commits