[Lldb-commits] [clang] [lldb] [llvm] [AArch64][TargetParser] autogen ArchExtKind enum - renaming (PR #90320)

2024-05-02 Thread Jonathan Thackray via lldb-commits
https://github.com/jthackray approved this pull request. LGTM (presumably these were mechanically renamed, given the diff size). https://github.com/llvm/llvm-project/pull/90320 ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llv

[Lldb-commits] [clang] [lldb] [llvm] [AArch64][TargetParser] autogen ArchExtKind enum - renaming (PR #90320)

2024-05-03 Thread Jonathan Thackray via lldb-commits
jthackray wrote: > The command-line names or FEAT_ names should probably be what we are aiming > for if we are changing them one-way or the other. Yes, standardising on FEAT_* names would be good to match the TRM, so we avoid the AEK_PREDRES/FEAT_SPECRES, AEK_PERFMON/FEAT_PMUv3, etc. mismatche

[Lldb-commits] [lldb] [llvm] [AArch64] move extension information into tablgen (PR #90987)

2024-05-07 Thread Jonathan Thackray via lldb-commits
@@ -11,42 +11,123 @@ // A SubtargetFeature that can be toggled from the command line, and therefore // has an AEK_* entry in ArmExtKind. +// +// If Function MultiVersioning (FMV) properties are left at their defaults +// (FEAT_INIT, no dependencies, priority 0) it indiates tha