[llvm-branch-commits] [lldb] [lldb][RISCV] update RISCV target features in disassembler (PR #173047)

[David Spickett via llvm-branch-commits]

https://github.com/DavidSpickett commented:

Looks ok to me, small test improvement if you are able to but if not no worries.

The new tests are failing CI, see the comment above this (CI always updates the same comment, so it can be further up the page than you'd expect).

That CI job is x86 hosted and it *looks* like the AArch64 hosted job succeeded but that is just a side effect of it being always marked green due to some ongoing instability.

One of the failures from AArch64:
```
2026-02-11T14:10:22.3288453Z gmake: Entering directory '/home/gha/actions-runner/_work/llvm-project/llvm-project/build/lldb-test-build.noindex/riscv/conflicting-extensions-disassembly/TestConflictingExtensions.test_conflicting_extensions_dwo'
2026-02-11T14:10:22.3289806Z /home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/riscv/conflicting-extensions-disassembly/Makefile:17: warning: overriding recipe for target 'a.out'
2026-02-11T14:10:22.3290601Z Makefile.rules:565: warning: ignoring old recipe for target 'a.out'
2026-02-11T14:10:22.3293898Z /home/gha/actions-runner/_work/llvm-project/llvm-project/build/bin/clang -g -O0 -m64 -I/home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/packages/Python/lldbsuite/test/make/../../../../..//include -I/home/gha/actions-runner/_work/llvm-project/llvm-project/build/tools/lldb/include -I/home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/riscv/conflicting-extensions-disassembly -I/home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/packages/Python/lldbsuite/test/make -include /home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/packages/Python/lldbsuite/test/make/test_common.h -fno-limit-debug-info -gsplit-dwarf -D_DEFAULT_SOURCE -march=rv64gc -g -c /home/gha/actions-runner/_work/llvm-project/llvm-project/lldb/test/API/riscv/conflicting-extensions-disassembly/main.c -o main.o
2026-02-11T14:10:22.3297054Z error: unknown target CPU 'rv64gc'
2026-02-11T14:10:22.3299876Z note: valid target CPU values are: nocona, core2, penryn, bonnell, atom, silvermont, slm, goldmont, goldmont-plus, tremont, nehalem, corei7, westmere, sandybridge, corei7-avx, ivybridge, core-avx-i, haswell, core-avx2, broadwell, skylake, skylake-avx512, skx, cascadelake, cooperlake, cannonlake, icelake-client, rocketlake, icelake-server, tigerlake, sapphirerapids, alderlake, raptorlake, meteorlake, arrowlake, arrowlake-s, lunarlake, gracemont, pantherlake, wildcatlake, novalake, sierraforest, grandridge, graniterapids, graniterapids-d, emeraldrapids, clearwaterforest, diamondrapids, knl, knm, k8, athlon64, athlon-fx, opteron, k8-sse3, athlon64-sse3, opteron-sse3, amdfam10, barcelona, btver1, btver2, bdver1, bdver2, bdver3, bdver4, znver1, znver2, znver3, znver4, znver5, x86-64, x86-64-v2, x86-64-v3, x86-64-v4
```
Same thing.

I don't recall having to set a CPU value for other tests. -march was usually enough.

https://github.com/llvm/llvm-project/pull/173047