Skip to content

Conversation

@vtjnash
Copy link
Member

@vtjnash vtjnash commented Mar 21, 2025

The unsafe_load code tries to reuse some of the logic from safe loads, but needs to be careful to override the parts that are not safe with slower versions of them. Similar to the typo-fix from ec3c02a on v1.11-backports.

Seen in the IR for

code_llvm(optimize=false, raw=true, unsafe_load, (Ptr{Tuple{UInt128}},))

causing LightBSON to fail.

Fix ancapdev/LightBSON.jl#37

The unsafe_load code tries to reuse some of the logic from safe loads,
but needs to be careful to override the parts that are not safe with
slower versions of them. Similar to the typo-fix from
ec3c02a on v1.11-backports.

Seen in the IR for
   code_llvm(optimize=false, raw=true, unsafe_load, (Ptr{Tuple{UInt128}},))
causing LightBSON to fail.

Fix ancapdev/LightBSON.jl#37
@vtjnash vtjnash added compiler:codegen Generation of LLVM IR and native code backport 1.12 Change should be backported to release-1.12 labels Mar 21, 2025
@vtjnash vtjnash requested a review from gbaraldi March 21, 2025 00:20
@vtjnash vtjnash merged commit 36b046d into master Mar 21, 2025
8 of 10 checks passed
@vtjnash vtjnash deleted the jn/LightBSON-37 branch March 21, 2025 20:55
KristofferC pushed a commit that referenced this pull request Mar 22, 2025
…7845)

The unsafe_load code tries to reuse some of the logic from safe loads,
but needs to be careful to override the parts that are not safe with
slower versions of them. Similar to the typo-fix from
ec3c02a on v1.11-backports.

Seen in the IR for

    code_llvm(optimize=false, raw=true, unsafe_load, (Ptr{Tuple{UInt128}},))

causing LightBSON to fail.

Fix ancapdev/LightBSON.jl#37

(cherry picked from commit 36b046d)
@KristofferC KristofferC removed the backport 1.12 Change should be backported to release-1.12 label Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

compiler:codegen Generation of LLVM IR and native code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Segfaults in tests on upcoming 1.12

3 participants