[RISCV][MC][NFC] Update IME vtype layout to match latest spec `riscv-isa-release-fa55752-2026-05-04` (#195998)
This updates the IME-specific vtype field layout to match the [latest
IME spec, version
riscv-isa-release-fa55752-2026-05-04](https://github.com/riscv/integrated-matrix-extension/blob/main/src/integrated-matrix.adoc#new-fields-in-the-vector-type-vtype-register).
The latest spec places the IME fields as:
| Field | New Position | Change Description |
|---------------|---------------------------|---------------------------------|
| `lambda[2:0]` | `vtype[XLEN-2:XLEN-4]` | Unchanged |
| `bs` | `vtype[XLEN-5]` | Moved from `vtype[XLEN-7]` |
| `altfmt_A` | `vtype[XLEN-6]` | Moved from `vtype[XLEN-5]` |
| `altfmt_B` | `vtype[XLEN-7]` | Moved from `vtype[XLEN-6]` |
Previously `bs`, `altfmt_A`, and `altfmt_B` followed the older ordering,
which was first introduced in #193956. The new position of altfmt
supports growing in the future for more datatypes.
This patch also updates tests to reflect field changes.
Currently this should be NFC since we didn't have any CodeGen
implementation that involves vtype in IME.
[libc][docs] Minor typos in Documentation (#196066)
- removed a duplicate "to" in dev/undefinde_behaviour.rst
- corrected "in order or link" to "inorder to link" in gpu/using.rst
Signed-off-by: udaykiriti <udaykiriti624 at gmail.com>
[InstCombine] Drop alignment assumptions more aggressively (#196060)
`computeKnownBits` gets a context instruction now, which allows dropping
assumes based on previous assumes.
[IR] Fix null pointer dereference in Constant::toConstantRange() for ConstantByte (#193874)
In the ConstantVector path of toConstantRange(), the code checks that
each element is either a ConstantInt or ConstantByte but unconditionally
dereferences the ConstantInt pointer to get the value. When the element
is a ConstantByte, the ConstantInt pointer is null, causing a crash.
This was introduced in 57568c288dbe when ConstantByte support was added
to toConstantRange() but the fallback to CB->getValue() was missed.
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply at anthropic.com>
[GlobalISel][AArch64] Allow bitcasts between fp types. (#196195)
This was failing the verifier as it was not considering different fp
types as a valid conversion for a bitcast.
[RISCV][GISel] Legalize G_IS_FPCLASS for fp128 (#195738)
When compiling `libc/src/stdlib/strtold.cpp` with GlobalISel there is a
failure. Calls to `@llvm.is.fpclass.f128` are translated to
G_IS_FPCLASS, which couldn't be laglized.
This PR tries to address that.
[clang-tidy] Improve redundant-casting check for binary operation (#191386)
Mark explicit casting as readabily redundant for a BinaryOperation with
atleast one operand of the same type as the cast type in
`RedundantCastingCheck`
E.g.; `static<float>(1 + 2.0f)` // redundant cast
Fixes #182132
[Instrumentor] Allow multiple config files with different filters
To instrument different functions in different ways we allow to provide
multiple config files now. Each file will result in one instrumentation
run. Multiple files can be passed via command line option or listed in
a "summary" file that is passed via command line option (to keep the
command length managable).