aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp
diff options
context:
space:
mode:
authorTomas Matheson <Tomas.Matheson@arm.com>2025-06-11 11:45:23 +0100
committerGitHub <noreply@github.com>2025-06-11 11:45:23 +0100
commit40cc7b4578fd2d65aaef8356fbe7caf2d84a8f3e (patch)
tree11e56196670de09e8359ac081ae73940bc14eb5e /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp
parent79a72c47d09c2e2cee645430f9d290c20d2618f1 (diff)
downloadllvm-40cc7b4578fd2d65aaef8356fbe7caf2d84a8f3e.zip
llvm-40cc7b4578fd2d65aaef8356fbe7caf2d84a8f3e.tar.gz
llvm-40cc7b4578fd2d65aaef8356fbe7caf2d84a8f3e.tar.bz2
[clang][AArch64] test -cc1 -print-enabled-extensions (#143570)
This adds tests that document how -cc1 and -print-enabled-extensions interact. The current behaviour looks wrong, and is caused by the fact that --print-enabled-extensions uses the MC subtarget feature API to determine the list of extensions to print, whereas the frontend uses the TargetParser API. The latter does no dependency expansion for the -target-feature flags but the MC API does. This doesn't fix anything but at least it documents the current behaviour, and will serve as a pre-commit test for any future fixes.
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationServerCommon.cpp')
0 files changed, 0 insertions, 0 deletions