MIPS/testsuite: mips16-thunks: Use `standard_output_file'
authorMaciej W. Rozycki <macro@imgtec.com>
Wed, 21 Sep 2016 11:55:25 +0000 (12:55 +0100)
committerMaciej W. Rozycki <macro@imgtec.com>
Wed, 21 Sep 2016 11:59:33 +0000 (12:59 +0100)
commit3d0ec882241884d0cabb27f8fee1262dbc7cf9e7
tree7412583a20d28a6cc9a95fd3ec86b4fb1d7df1ab
parentfc6cda2ee85d2c2719db3b5ae3a1ae963f28416b
MIPS/testsuite: mips16-thunks: Use `standard_output_file'

Correct a commit 2151ccc56c74 ("Always organize test artifacts in a
directory hierarchy") regression causing:

Running .../gdb/testsuite/gdb.arch/mips16-thunks.exp ...
gdb compile failed, Assembler messages:
Fatal error: can't create .../gdb/testsuite/gdb.arch/mips16-thunks-inmain.o: No such file or directory
gdb compile failed, Assembler messages:
Fatal error: can't create .../gdb/testsuite/gdb.arch/mips16-thunks-main.o: No such file or directory
gdb compile failed, mips-mti-linux-gnu-gcc: error: .../gdb/testsuite/gdb.arch/mips16-thunks-inmain.o: No such file or directory
mips-mti-linux-gnu-gcc: error: .../gdb/testsuite/gdb.arch/mips16-thunks-main.o: No such file or directory
UNSUPPORTED: gdb.arch/mips16-thunks.exp: No MIPS16 support in the toolchain.

by using `standard_output_file' to construct output file names
throughout.

gdb/testsuite/
* gdb.arch/mips16-thunks.exp: Use `standard_output_file'
throughout.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.arch/mips16-thunks.exp