Add //testing/perf and fix up output file location in yasm_assemble.gni.

third_party/yasm/yasm_assemble.gni

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # This provides the yasm_assemble() template which uses YASM to assemble
 # assembly files.
 #
 # Files to be assembled with YASM should have an extension of .asm.
 #
 # Parameters
@@ skipping 143 matching lines @@
       }
     }
 
     # Output file.
     #
     # TODO(brettw) it might be nice if there was a source expansion for the
     # path of the source file relative to the source root. Then we could
     # exactly duplicate the naming and location of object files from the
     # native build, which would be:
     # "$root_out_dir/${target_name}.{{source_dir_part}}.$asm_obj_extension"
-    outputs = [ "$target_out_dir/{{source_name_part}}.o" ]
+    outputs = [ "$target_gen_dir/{{source_name_part}}.o" ]

[brettw, 2014/07/08 21:11:48]

Why change this? The out dir is where the normal .o files go, so it seems like
yasm should put them there as well.

     args += [
       "-o", rebase_path(outputs[0], root_build_dir),
       "{{source}}"
     ]
 
     # The wrapper script run_yasm will write the depfile to the same name as
     # the output but with .d appended (like gcc will).
     depfile = outputs[0] + ".d"
   }
 
   # Gather the .o files into a linkable thing. This doesn't actually link
   # anything (a source set just compiles files to link later), but will pass
   # the object files generated by the action up the dependency chain.
   source_set(source_set_name) {
     if (defined(invoker.visibility)) {
       visibility = invoker.visibility
     }
 
     sources = get_target_outputs(":$action_name")
   }
 }