aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base
diff options
context:
space:
mode:
authorYao Qi <yao.qi@linaro.org>2015-07-07 16:58:19 +0100
committerYao Qi <yao.qi@linaro.org>2015-07-07 16:58:19 +0100
commit71be1fdc3655a170f4b14d795e5c9e81fcea06ef (patch)
treed11ebea81ab430ffa8e3c77fc125a6bfd05586ac /gdb/testsuite/gdb.base
parent82c40d4b1deb252f2d17ff74f3fae6ae8cdd0383 (diff)
downloadbinutils-71be1fdc3655a170f4b14d795e5c9e81fcea06ef.zip
binutils-71be1fdc3655a170f4b14d795e5c9e81fcea06ef.tar.gz
binutils-71be1fdc3655a170f4b14d795e5c9e81fcea06ef.tar.bz2
Adjust gdb.multi tests for aarch64
Multi-arch related tests under gdb.multi are to compile programs with the same compiler but different compiler options (-m64 vs -m32). However, different compilers are needed to compile both aarch64 program and arm (aarch32) program. This patch is to adjust these test cases to compile programs in different modes with different compiler. When we use gcc for arm-linux target, its file name can be different, arm-linux-gnueabihf-gcc, arm-linux-gnueabi-gcc, or arm-none-linux-gnueabi-gcc, so I add a variable ARM_CC_FOR_TARGET, so that user can set the name of gcc for arm-linux target on aarch64, like: $ make check RUNTESTFLAGS='ARM_CC_FOR_TARGET=arm-linux-gnueabihf-gcc multi-arch.exp' gdb/testsuite: 2015-07-07 Yao Qi <yao.qi@linaro.org> * gdb.multi/multi-arch-exec.exp: Set march1 and march2 to "" if target is aarch64. If target is aarch64, set compiler=${ARM_CC_FOR_TARGET} if it exists. * gdb.multi/multi-arch.exp: Likewise.
Diffstat (limited to 'gdb/testsuite/gdb.base')
0 files changed, 0 insertions, 0 deletions