Releases: predators46/llvm-project
Releases · predators46/llvm-project
rustc-15.0.0: [DwarfEhPrepare] Assign dummy debug location for inserted _Unwind_Res…
…ume calls (PR57469) DwarfEhPrepare inserts calls to _Unwind_Resume into landing pads. If _Unwind_Resume happens to be defined in the same module and debug info is used, then this leads to a verifier error: inlinable function call in a function with debug info must have a !dbg location call void @_Unwind_Resume(ptr %exn.obj) #0 Fix this by assigning a dummy location to the call. (As this happens in the backend, inlining is not actually relevant here.) Fixes https://github.com/llvm/llvm-project/issues/57469. Differential Revision: https://reviews.llvm.org/D133095 (cherry picked from commit 5134bd432f8c35c87f4c4dc3bb744d396adcab58)
14.0.5: [AST] Don't assert instruction reads/writes memory (PR51333)
This function is well-defined for an instruction that doesn't access memory (and thus trivially doesn't alias anything in the AST), so drop the assert. We can end up with a readnone call here if we originally created a MemoryDef for an indirect call, which was later replaced with a direct readnone call. Fixes https://github.com/llvm/llvm-project/issues/51333. Differential Revision: https://reviews.llvm.org/D127947 (cherry picked from commit 560e694d48a6020f613281c29ffd17184f56dfb0)
rustc-14.0.5: [AST] Don't assert instruction reads/writes memory (PR51333)
This function is well-defined for an instruction that doesn't access memory (and thus trivially doesn't alias anything in the AST), so drop the assert. We can end up with a readnone call here if we originally created a MemoryDef for an indirect call, which was later replaced with a direct readnone call. Fixes https://github.com/llvm/llvm-project/issues/51333. Differential Revision: https://reviews.llvm.org/D127947 (cherry picked from commit 560e694d48a6020f613281c29ffd17184f56dfb0)