Gut gyp_chromium, common.gypi.

docs/profiling_content_shell_on_android.md

 # Profiling Content Shell on Android
 
 Below are the instructions for setting up profiling for Content Shell on
 Android. This will let you generate profiles for ContentShell. This will require
 linux, building an userdebug Android build, and wiping the device.
 
 [TOC]
 
 ## Prepare your device.
 
@@ skipping 59 matching lines @@
 If you get the error `error: device offline`, you may need to become a developer
 on your device before Linux will see it. On Jellybean 4.2.1 and above this
 requires going to “about phone” or “about tablet” and clicking the build number
 7 times:
 http://androidmuscle.com/how-to-enable-usb-debugging-developer-options-on-nexus-4-and-android-4-2-devices/
 
 ## Enable profiling
 
 Rebuild `content_shell_apk` with profiling enabled.
 
-With GYP (deprecated):
-
-    export GYP_DEFINES="$GYP_DEFINES profiling=1"
-    build/gyp_chromium
-    ninja -C out/Release content_shell_apk
-
 With GN:
 
     gn args out/Profiling
     # add "enable_profiling = true"
     ninja -C out/Profiling content_shell_apk
     export CHROMIUM_OUTPUT_DIR="$PWD/out/Profiling"
 
 ## Run a Telemetry perf profiler
 
 You can run any Telemetry benchmark with `--profiler=perf`, and it will:
@@ skipping 94 matching lines @@
 ## Create the report
 
 1.  Run the following:
 
     ```
     ./perfhost_linux report -g -i perf.data --symfs symbols/
     ```
 
 1.  If you don’t see chromium/webkit symbols, make sure that you built/pushed
     Release, and that the symlink you created to the .so is valid!
-1.  If you have symbols, but your callstacks are nonsense, make sure you ran
-    `build/gyp_chromium` after setting `profiling=1`, and rebuilt.
 
 ## Add symbols for the kernel
 
 1.  By default, /proc/kallsyms returns 0 for all symbols, to fix this, set
     `/proc/sys/kernel/kptr_restrict` to `0`:
 
     ```
     adb shell echo “0” > /proc/sys/kernel/kptr_restrict
     ```
 
 1.  See http://lwn.net/Articles/420403/ for explanation of what this does.
 
     ```
     adb pull /proc/kallsyms symbols/kallsyms
     ```
 
 1.  Now add --kallsyms to your perfhost\_linux command:
     ```
     ./perfhost_linux report -g -i perf.data --symfs symbols/ \
         --kallsyms=symbols/kallsyms
     ```