Add memory tagging testcases
authorLuis Machado <luis.machado@linaro.org>
Mon, 15 Jun 2020 18:55:02 +0000 (15:55 -0300)
committerLuis Machado <luis.machado@linaro.org>
Wed, 24 Mar 2021 18:09:59 +0000 (15:09 -0300)
commitbf0aecce6ebc7182b0cfd36773bca622e2a19c3e
treef5c548df37491eeb53910e3af8aa9bce3ff9c763
parentce192338645499d4ed5a9a3a9f8105f0135a7cfd
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.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.arch/aarch64-mte.c [new file with mode: 0644]
gdb/testsuite/gdb.arch/aarch64-mte.exp [new file with mode: 0644]
gdb/testsuite/gdb.base/memtag.c [new file with mode: 0644]
gdb/testsuite/gdb.base/memtag.exp [new file with mode: 0644]
gdb/testsuite/lib/gdb.exp