[gdb/testsuite] Fix gdb.dwarf2/entry-value-typedef.exp with -m32
authorTom de Vries <tdevries@suse.de>
Thu, 13 Oct 2022 08:03:09 +0000 (10:03 +0200)
committerTom de Vries <tdevries@suse.de>
Thu, 13 Oct 2022 08:03:09 +0000 (10:03 +0200)
commit927b2f4caf46e5ca49684c9a52a9786425c60fa2
tree1215d52e4c181329372f9344cb4bddf4ddfb38f4
parent0ffa92773a25042d97a6df74062270a03cb84982
[gdb/testsuite] Fix gdb.dwarf2/entry-value-typedef.exp with -m32

With test-case gdb.dwarf2/entry-value-typedef.exp and target board unix/-m32,
I run into:
...
builtin_spawn -ignore SIGHUP g++ -fno-stack-protector \
  gdb/testsuite/gdb.dwarf2/entry-value-typedef-amd64.S \
  -fdiagnostics-color=never -Lbuild/libiberty -lm -m32 \
  -o outputs/gdb.dwarf2/entry-value-typedef/entry-value-typedef^M
entry-value-typedef.cpp: Assembler messages:^M
entry-value-typedef.cpp:38: Error: bad register name `%rbp'^M
...

The problem is that the test-cases selects an amd64 .S file based on the check:
...
if { [istarget "x86_64-*-linux*"] } {
...
which is also true for target board unix/-m32 on x86_64-linux.

Fix this by adding the missing is_lp64_target check.

Tested on x86_64-linux, using native and target board unix/-m32.
gdb/testsuite/gdb.dwarf2/entry-value-typedef.exp