Google Git
Sign in
fuchsia / third_party / github.com / llvm / llvm-project / refs/heads/users/jthackray/with-precommit
commitd6b9930fdacbc7b502879c9132713aac2ff28285[log] [tgz]
authorJonathan Thackray <jonathan.thackray@arm.com>Sat Feb 07 22:54:50 2026 +0000
committerJonathan Thackray <jonathan.thackray@arm.com>Wed Feb 11 12:15:08 2026 +0000
tree448e07339e356409b54cc8136446a3cf62d3dc22
parent7e34aaeb91cfd537f8510c94c51df31ecd310ba5 [diff]
[AArch64][llvm] Preserve FP_TO_*_SAT VT operand in SVE scalar-combine

Updated RUN lines and generated new `CHECK‑SME`/`CHECK‑SVE` lines in:

    llvm/test/CodeGen/AArch64/arm64-cvt-simd-fptoi.ll
    llvm/test/CodeGen/AArch64/arm64-cvtf-simd-itofp.ll

by adding `-force-streaming` and `-force-streaming-compatible` runs,
as pre-commit tests for a future change to enable FPRCVT streaming.

This triggers a SVE scalar-combine path which requires a code update.
FP_TO_*_SAT nodes require operand 1 (the saturation VT) to be present.
Without it the node is malformed and hits the SelectionDAG assertion
“Invalid child # of SDNode!”.

Also, skip the SVE combine if the scalar/custom op is already legal.
3 files changed
tree: 448e07339e356409b54cc8136446a3cf62d3dc22
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cross-project-tests/
  9. flang/
  10. flang-rt/
  11. libc/
  12. libclc/
  13. libcxx/
  14. libcxxabi/
  15. libsycl/
  16. libunwind/
  17. lld/
  18. lldb/
  19. llvm/
  20. llvm-libgcc/
  21. mlir/
  22. offload/
  23. openmp/
  24. orc-rt/
  25. polly/
  26. runtimes/
  27. third-party/
  28. utils/
  29. .clang-format
  30. .clang-format-ignore
  31. .clang-tidy
  32. .git-blame-ignore-revs
  33. .gitattributes
  34. .gitignore
  35. .mailmap
  36. CODE_OF_CONDUCT.md
  37. CONTRIBUTING.md
  38. LICENSE.TXT
  39. pyproject.toml
  40. README.md
  41. SECURITY.md
README.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

Welcome to the LLVM project!

This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.

The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.

C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.

Other components include: the libc++ C++ standard library, the LLD linker, and more.

Getting the Source Code and Building LLVM

Consult the Getting Started with LLVM page for information on building and running LLVM.

For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.

Getting in touch

Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.

The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.