Skip to content

DO NOT MERGE: v1.12 branch for comparison to master #202

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

Draft
wants to merge 325 commits into
base: master
Choose a base branch
from

Conversation

nickrobinson251
Copy link
Member

@nickrobinson251 nickrobinson251 commented Jan 15, 2025

@nickrobinson251 nickrobinson251 force-pushed the v1.12.0-DEV+RAI branch 4 times, most recently from 966538b to 9da665d Compare January 29, 2025 13:01
@DelveCI DelveCI force-pushed the v1.12.0-DEV+RAI branch 7 times, most recently from 1cff7d7 to 1e6e20d Compare February 7, 2025 00:28
@DelveCI DelveCI force-pushed the v1.12.0-DEV+RAI branch 5 times, most recently from 02e0f68 to 35024c5 Compare February 18, 2025 00:28
@DelveCI DelveCI force-pushed the v1.12.0-DEV+RAI branch 4 times, most recently from fb189dc to 7e4f1cb Compare February 27, 2025 00:29
vtjnash and others added 8 commits March 3, 2025 13:59
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)
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]>
@DelveCI DelveCI force-pushed the v1.12.0-DEV+RAI branch from 1bc440d to c5b6b8d Compare May 28, 2025 00:33
gbaraldi and others added 27 commits May 28, 2025 11:11
…8412)

These are used by `hasmethod`, and in any case including keyword
argument symbols is unavoidable so there is no cost to keeping these.

(cherry picked from commit c5df018)
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)
Update branch info to `release-1.12`, so that we can bump the SparseArrays.jl stdlib.
…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]>
@DelveCI DelveCI force-pushed the v1.12.0-DEV+RAI branch from c5b6b8d to 875ac9c Compare May 29, 2025 00:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.