The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0454d1c39637beb1fb084bea057d614f6908a7ae

commit 0454d1c39637beb1fb084bea057d614f6908a7ae
Author: inglorion <inglorion@chromium.org>
Date: Fri Dec 02 23:04:19 2016

Add the possibility to build with PGO when using Clang

r257133 introduced chrome_pgo_phase to allow building Chrome with
profile-guided optimization. Thus far, support for this has only
been implemented for MSVC on Windows. This change allows PGO to
be used with Clang, as well.

BUG= 666152 

Review-Url: https://codereview.chromium.org/2507333002
Cr-Commit-Position: refs/heads/master@{#436067}

[modify] https://crrev.com/0454d1c39637beb1fb084bea057d614f6908a7ae/build/config/compiler/compiler.gni
[add] https://crrev.com/0454d1c39637beb1fb084bea057d614f6908a7ae/build/config/compiler/pgo/BUILD.gn
[add] https://crrev.com/0454d1c39637beb1fb084bea057d614f6908a7ae/build/config/compiler/pgo/pgo.gni
[modify] https://crrev.com/0454d1c39637beb1fb084bea057d614f6908a7ae/chrome/BUILD.gn

Sebastian pointed me to this bug. Just wanted to mention that on Chrome OS we use AFDO (sampled PGO) with Clang. We currently train using benchmarks. We are working in a project to get PGO training set from profiles from the field. Also finding a set of benchamarks that aproximate user behavior. Maybe you can use some of this when you are ready.

Archiving P3s older than 1 year with no owner or component.