Use standard_output_file in a couple more places

I noticed a few files left over in the testsuite/ directory in the
build tree after running tests.  Normally output files should not wind
up there, but instead should end up in the test's subdirectory.  This
isn't always crucial, but in the past there were problems with tests
clashing, preventing parallel runs, and so it is better to be clean
here.

This patch changes a couple of tests to use standard_output_file to
fix this problem.

Tested by re-running the tests in question and examining the
directory.

gdb/testsuite/ChangeLog
2018-10-06  Tom Tromey  <tom@tromey.com>

	* gdb.base/gnu-ifunc.exp (build): Use standard_output_file.
	* gdb.trace/unavailable-dwarf-piece.exp: Use standard_output_file.

gdb/testsuite/ChangeLog

@@ -1,3 +1,8 @@
+2018-10-06  Tom Tromey  <tom@tromey.com>
+
+	* gdb.base/gnu-ifunc.exp (build): Use standard_output_file.
+	* gdb.trace/unavailable-dwarf-piece.exp: Use standard_output_file.
+
 2018-10-06  Tom Tromey  <tom@tromey.com>
 
 	* gdb.python/py-breakpoint.exp (check_last_event): Check location

gdb/testsuite/gdb.base/gnu-ifunc.exp

@@ -76,7 +76,7 @@ proc build {resolver_attr resolver_debug final_debug} {
 	lappend final_opts "debug"
     }
 
-    set final_o $final_file-$suffix.o
+    set final_o [standard_output_file $final_file-$suffix.o]
 
     if { [gdb_compile_shlib ${srcdir}/${subdir}/$libsrc \
 	      $lib_so $lib_opts] != ""

gdb/testsuite/gdb.trace/unavailable-dwarf-piece.exp

@@ -22,7 +22,7 @@ if {![dwarf2_support]} {
 
 standard_testfile .c
 
-set asm_file "${testfile}-dbg.s"
+set asm_file [standard_output_file "${testfile}-dbg.s"]
 set opts {}
 
 if  { [gdb_compile ${srcdir}/${subdir}/${srcfile} ${binfile}1.o \