]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit
Add memory tagging testcases users/luisgpm/aarch64-mte-v3
authorLuis Machado <luis.machado@linaro.org>
Mon, 15 Jun 2020 18:55:02 +0000 (15:55 -0300)
committerLuis Machado <luis.machado@linaro.org>
Thu, 16 Jul 2020 16:09:27 +0000 (13:09 -0300)
commit46195acfb8ca81c83522d3f1fb184eeeebf190c2
tree7923e525d1806e3554e3f2dda5197106ac9d74e9
parent59bdb29c7e125832578c03bf0e964b1dbffc964c
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:

YYYY-MM-DD  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/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