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.

Sign up for GitHub

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

Jump to bottom

Backports for 1.10.10 #57715

Open
wants to merge 7 commits into
base: release-1.10
Choose a base branch
from
Open

Backports for 1.10.10 #57715

wants to merge 7 commits into from
+227 −68

Conversation

KristofferC
Copy link
Member

Backported PRs:

Need manual backport:

Contains multiple commits, manual intervention needed:

Non-merged PRs with backport label:

inkydragon and others added 6 commits March 11, 2025 10:47
@inkydragon @KristofferC
docs: remove dirname.c from THIRDPARTY file (#56413)
0b28ceb 
- `dirname.c` was removed by
c2cec7a

(cherry picked from commit 85dc2c7)
@vchuravy @KristofferC
Only strip invariant.load from special pointers (#57386)
16137fd 
Other backends (in this case NVPTX) require that `invariant.load`
metadata is maintained to generate non-coherent loads.

Currently, we unconditionally strip that metadata from all loads,
since our other uses of it may have become invalid.

x-ref: llvm/llvm-project#112834
JuliaGPU/CUDA.jl#2531

---------

Co-authored-by: Gabriel Baraldi <baraldigabriel@gmail.com>
(cherry picked from commit 29da86b)
@barucden @KristofferC
Docs: circshift!(::AbstractVector, ::Integer) (#57539)
5ab4295 
Closes #46016

(cherry picked from commit b0323ab)
@nsajko @KristofferC
strings: type assert in the generic nextind, prevind methods (#57608
1a1dd13 
)

The type assertions are valid according to the doc strings of these
functions in the case of `AbstractString`.

Should prevent some invalidation on loading user code.

Fixes #57605

(cherry picked from commit 6c9c336)
@N5N3 @KristofferC
Intersect: try normal+reverse+existential subtyping during intersecti…
2253945 
…on (#57476)

Typevars are all existential (in the sense of variable lb/ub) during
intersection. This fix is somehow costly as we have to perform 3 times
check to prove a false result. But a single existential <: seems too
dangerous as it cause many circular env in the past.
fix #57429
fix #41561

(cherry picked from commit beb928b)
@gbaraldi @KristofferC
Make sure we don't promise alignments that are larger than the heap a…
eb272a3 
…lignment to LLVM (#56938)

Fixes #56937

---------

Co-authored-by: Oscar Smith <oscardssmith@gmail.com>
(cherry picked from commit 1e2758e)
@KristofferC KristofferC added the release Release management and versioning. label Mar 11, 2025
@vtjnash
fix alignment computation for nested objects (#57722)
5451622 
The alignment of a nested object (in C layouts) is not affected by the
alignment of its parent container when computing a field offset (as if
it will be allocated at address 0). This can be strongly
counter-intuitive (as it implies it should add padding where it does not
seem to provide value to the user), but this is required to match the C
standard. It also permits users to write custom allocators which happen
to provide alignment in excess of that which codegen may assume is
guaranteed, and get the behavioral characteristics they intended to
specify (without resorting to computing explicit padding).

Addresses
#57713 (comment)

(Cherry-picked from ec3c02a in
v1.11 backports branch)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
release Release management and versioning.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
8 participants
@KristofferC @inkydragon @vchuravy @barucden @nsajko @N5N3 @gbaraldi @vtjnash