aboutsummaryrefslogtreecommitdiff
path: root/gdb/gdbarch.c
diff options
context:
space:
mode:
authorLuis Machado <luis.machado@linaro.org>2020-06-15 15:55:02 -0300
committerLuis Machado <luis.machado@linaro.org>2021-03-24 15:09:59 -0300
commitbf0aecce6ebc7182b0cfd36773bca622e2a19c3e (patch)
treef5c548df37491eeb53910e3af8aa9bce3ff9c763 /gdb/gdbarch.c
parentce192338645499d4ed5a9a3a9f8105f0135a7cfd (diff)
downloadgdb-bf0aecce6ebc7182b0cfd36773bca622e2a19c3e.zip
gdb-bf0aecce6ebc7182b0cfd36773bca622e2a19c3e.tar.gz
gdb-bf0aecce6ebc7182b0cfd36773bca622e2a19c3e.tar.bz2
Add memory tagging testcases
Add an AArch64-specific test and a more generic memory tagging test that other architectures can run. Even though architectures not supporting memory tagging can run the memory tagging tests, the runtime check will make the tests bail out early, as it would make no sense to proceed without proper support. It is also tricky to do any further runtime tests for memory tagging, given we'd need to deal with tags, and those are arch-specific. Therefore the test in gdb.base is more of a smoke test. If an architecture wants to implement memory tagging, then it makes sense to have tests within gdb.arch instead. gdb/testsuite/ChangeLog: 2021-03-24 Luis Machado <luis.machado@linaro.org> * gdb.arch/aarch64-mte.c: New file. * gdb.arch/aarch64-mte.exp: New test. * gdb.base/memtag.c: New file. * gdb.base/memtag.exp: New test. * lib/gdb.exp (supports_memtag): New function.
Diffstat (limited to 'gdb/gdbarch.c')
0 files changed, 0 insertions, 0 deletions