mirror of https://github.com/llvm/llvm-project.git synced 2025-04-24 23:06:05 +00:00

[llvm] Match llvm.type.checked.load.relative semantics to llvm.load.r… (#129583 )

…elative

The semantics of `llvm.type.checked.load.relative` seem to be a little
different from that of `llvm.load.relative`. It looks like the semantics
for `llvm.type.checked.load.relative` is `ptr + offset + *(ptr +
offset)` whereas the semantics for `llvm.load.relative` is `ptr + *(ptr
+ offset)`. That is, the offset for the former is added to the offset
address whereas the later has the offset added to the original pointer.

It really feels like the checked intrinsic was meant to match the
semantics of the non-checked intrinsic, but I think for all cases the
checked intrinsic is used (swift being the only use I know of), the
calculation just happens to be the same because swift always uses an
offset of zero. Likewise, all llvm tests for this intrinsic happen to
use an offset of zero.

Relative vtables in clang happens to be the first time where we're using
this intrinsic and using it with non-zero values. This updates the
semantics of the checked intrinsic to match the non-checked one.
Effectively this shouldn't change any codegen by any users of this since
all current users seem to use a zero offset.

This PR also updates some tests with non-zero offsets.

2025-03-13 14:50:41 -07:00

6.8 KiB

Raw Blame History

LLVM {{env.config.release}} Release Notes

```{warning} These are in-progress notes for the upcoming LLVM {{env.config.release}}
             release. Release notes for previous releases can be found on
             [the Download Page](https://releases.llvm.org/download.html).
```

Introduction

This document contains the release notes for the LLVM Compiler Infrastructure, release {{env.config.release}}. Here we describe the status of LLVM, including major improvements from the previous release, improvements in various subprojects of LLVM, and some of the current users of the code. All LLVM releases may be downloaded from the LLVM releases web site.

For more information about LLVM, including information about the latest release, please check out the main LLVM web site. If you have questions or comments, the Discourse forums is a good place to ask them.

Note that if you are reading this file from a Git checkout or the main LLVM web page, this document applies to the next release, not the current one. To see the release notes for a specific release, please see the releases page.

Non-comprehensive list of changes in this release

Changes to the LLVM IR

The nocapture attribute has been replaced by captures(none).
The constant expression variants of the following instructions have been removed:
- mul
Updated semantics of llvm.type.checked.load.relative to match that of llvm.load.relative.

Changes to LLVM infrastructure

Removed support for target intrinsics being defined in the target directories themselves (i.e., the TargetIntrinsicInfo class).

Changes to building LLVM

Changes to TableGen

Changes to Interprocedural Optimizations

Changes to the AArch64 Backend

Changes to the AMDGPU Backend

Changes to the ARM Backend

Changes to the AVR Backend

Changes to the DirectX Backend

Changes to the Hexagon Backend

Changes to the LoongArch Backend

Changes to the MIPS Backend

Changes to the PowerPC Backend

Changes to the RISC-V Backend

Adds experimental assembler support for the Qualcomm uC 'Xqcili` (Load Large Immediate) extension.
Adds experimental assembler support for the Qualcomm uC 'Xqcilia` (Large Immediate Arithmetic) extension.
Adds experimental assembler support for the Qualcomm uC 'Xqcibm` (Bit Manipulation) extension.
Adds experimental assembler and code generation support for the Qualcomm 'Xqccmp' extension, which is a frame-pointer convention compatible version of Zcmp.
Added non-quadratic log-vrgather cost model for vrgather.vv instruction

Changes to the WebAssembly Backend

Changes to the Windows Target

fp128 is now passed indirectly, meaning it uses the same calling convention as i128.

Changes to the X86 Backend

Changes to the OCaml bindings

Changes to the Python bindings

Changes to the C API

The following functions for creating constant expressions have been removed, because the underlying constant expressions are no longer supported. Instead, an instruction should be created using the LLVMBuildXYZ APIs, which will constant fold the operands if possible and create an instruction otherwise:
- LLVMConstMul
- LLVMConstNUWMul
- LLVMConstNSWMul

Changes to the CodeGen infrastructure

Changes to the Metadata Info

Changes to the Debug Info

Changes to the LLVM tools

llvm-objcopy now supports the --update-section flag for intermediate Mach-O object files.
llvm-strip now supports continuing to process files on encountering an error.
In llvm-objcopy's ELF port, --discard-locals and --discard-all now allow and preserve symbols referenced by relocations.

Changes to LLDB

When building LLDB with Python support, the minimum version of Python is now 3.8.
LLDB now supports hardware watchpoints for AArch64 Windows targets. Windows does not provide API to query the number of supported hardware watchpoints. Therefore current implementation allows only 1 watchpoint, as tested with Windows 11 on the Microsoft SQ2 and Snapdragon Elite X platforms.
LLDB now steps through C++ thunks. This fixes an issue where previously, it wouldn't step into multiple inheritance virtual functions.

Changes to lldb-dap

Breakpoints can now be set for specific columns within a line.
Function return value is now displayed on step-out.

Changes to BOLT

Changes to Sanitizers

Other Changes

External Open Source Projects Using LLVM {{env.config.release}}

A project...

Additional Information

A wide variety of additional information is available on the LLVM web page, in particular in the documentation section. The web page also contains versions of the API documentation which is up-to-date with the Git version of the source code. You can access versions of these documents specific to this release by going into the llvm/docs/ directory in the LLVM tree.

If you have any questions or comments about LLVM, please feel free to contact us via the Discourse forums.

6.8 KiB Raw Blame History