diff options
author | Tomas Matheson <Tomas.Matheson@arm.com> | 2024-05-16 09:45:14 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-05-16 09:45:14 +0100 |
commit | 72a895336b1e4df1ec2f485f8786ead6c356edb8 (patch) | |
tree | edeec74adfbc01363d15aeeb72237960114b3308 /lldb/packages/Python/lldbsuite/test/configuration.py | |
parent | 51403ada789e63e98e0dd5ac0ceba351465490d1 (diff) | |
download | llvm-72a895336b1e4df1ec2f485f8786ead6c356edb8.zip llvm-72a895336b1e4df1ec2f485f8786ead6c356edb8.tar.gz llvm-72a895336b1e4df1ec2f485f8786ead6c356edb8.tar.bz2 |
[AArch64][TargetParser] move ArchInfo into tablegen [NFC] (#92037)
This moves the architecture version, profile and extension information
into tablegen, and generates the TargetParser ArchInfo objects from
this data.
There are two lists of "dependencies" defined for each architecture: the
SubtargetFeature::Implies which controls which features are
automatically enabled in the backend when the corresponding architecture
SubtargetFeature is enabled; and the list of Extensions which are
enabled by default for this architecture. As far as I can tell, the idea
here is that the SubtargetFeature models the mandatory dependencies (although
they can still be disabled if desired) while the default extensions models
the typical use case for that architecture.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions