This is the mail archive of the
mailing list for the GCC project.
Re: AutoFDO profile toolchain is open-sourced
- From: Ilya Palachev <i dot palachev at samsung dot com>
- To: Dehao Chen <dehao at google dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Cc: Vyacheslav Barinov <v dot barinov at samsung dot com>, David Li <davidxl at google dot com>, Diego Novillo <dnovillo at google dot com>
- Date: Tue, 07 Apr 2015 17:45:44 +0300
- Subject: Re: AutoFDO profile toolchain is open-sourced
- Authentication-results: sourceware.org; auth=none
- References: <CAO2gOZWydpiBXb=1QDyCRt-ybDieqy8X4S_+uRZk2Y2v+cFdYQ at mail dot gmail dot com>
Here are some questions about AutoFDO.
On 08.05.2014 02:55, Dehao Chen wrote:
We have open-sourced AutoFDO profile toolchain in:
For GCC developers, the most important tool is create_gcov, which
converts sampling based profile to GCC-readable profile. Please refer
to the readme file
In the mentioned README file it is said that " In order to collect this
profile, you will need to have an Intel CPU that have last branch record
(LBR) support." Is this information obsolete? Chrome Canary builds use
AutoFDO for ARMv7l
What about Aarch64 support? Is it supported?
To use the profile, one need to checkout
https://gcc.gnu.org/svn/gcc/branches/google/gcc-4_8. We are working on
porting AutoFDO to trunk
For now AutoFDO was merged into gcc-5.0 (trunk) branch.
Is it possible to backport it to 4.9 branch? Can you estimate required
efforts for that?
We have limited doc inside the open-sourced package, and we are
planning to add more content to the wiki page
(https://github.com/google/autofdo/wiki). Feel free to send me emails
or discuss on github if you have any questions.