| commit | 7e22180c20fa3b4e0add41ad620d2eaac2b47fcc | [log] [tgz] |
|---|---|---|
| author | Chandler Carruth <chandlerc@gmail.com> | Tue Jan 28 00:07:38 2025 -0800 |
| committer | GitHub <noreply@github.com> | Tue Jan 28 00:07:38 2025 -0800 |
| tree | 9a2766070b4c299b6ab071b16f148e835c34d8ce | |
| parent | 0865ecc5150b9a55ba1f9e30b6d463a66ac362a6 [diff] |
[StrTable] Mechanically convert Hexagon builtins to use TableGen (#123460) This switches them to use the common builtin TableGen emission. The fancy feature string preprocessor tricks are replaced with a fairly direct translation into TableGen. All of the actual definitions were created using a quite hack-y Python script that was never intended to be productionized. It preserves the order, spacing, and even comments from the original files. For posterity, the script used is here: https://gist.github.com/chandlerc/f53c7d735e33eecf388529bd9a6010df The original `.def` file appears to be generated by some out-of-tree `iset.py` script, which because it is out of tree I couldn't update. It should be very straightforward though to update it to generate a similar structure as was used to produce the `.td` file. In addition to helping move towards TableGen for all of the builtins, these builtins in particular can be *much* more efficiently handled using TableGen when we start emitting string tables for them because it allows de-duplicating all of the feature strings. The commit sha parent at the time the PR was made is 7253c6fde498c4c9470b681df47d46e6930d6a02 and at that commit, the resulting TableGen file produces a `.inc` file that only differs in whitespace and the order of the builtins defined.
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.
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.
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.