[RISCV][NFC] Push riscv_selectcc PatFrag Inwards (#175902)

`riscv_selectcc_frag` was a PatFrag with a transform to get a
`RISCVCC::CondCode` from the `riscv_selectcc` node. The pattern matched
the entire `riscv_selectcc` node, but the transform meant that the saved
value was just the condition code itself, which was not obvious (to me),
either from naming or from how the pattern was structured.

This change "pushes" the pattern fragment inwards to the condition code
it relates to using `riscv_cond:$cc` (a `cond` fragment with a
transform, only needed when defining the pattern directly with the
pseudo), or using the `CCtoRISCVCC` transform explicitly in the emit
side of the pattern.

IMO this makes the select handling quite a bit clearer, as the `$cc` in
the pattern and result more directly relates to the operand it matches
and represents. This has potentially swapped one source of confusion
noted above for the confusion of seeing `Cond:$cc` being used to bind
the specific condition code that has been provided at pattern
instantiation to `$cc`, so that it can be transformed before being
emitted.
7 files changed
tree: 7b15a3226f3d63ffdcf9a4c044203d8c7648fe4e
  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.