This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] AutoFDO patch for trunk


Everything will be the same on non-intel CPUs except for the perf command:

perf record -e instructions -- your program.

i.e. you need to drop "-b" and use instructions as event.

Note that the current algorithm is tuned for accurate instruction
level profile, which is not available on non-Intel CPU. But you are
more than welcome to tune the propagation algorithm to get most out of
inaccurate instruction profile.

Cheers,
Dehao

On Tue, Oct 21, 2014 at 12:30 PM, Markus Trippelsdorf
<markus@trippelsdorf.de> wrote:
> On 2014.10.20 at 14:21 -0700, Dehao Chen wrote:
>> >> +If @var{path} is specified, GCC looks at the @var{path} to find
>> >> +the profile feedback data files.
>> >> +
>> >> +In order to collect AutoFDO profile, you need to have:
>> >> +
>> >> +1. A linux system with linux perf support
>> >> +2. An Intel processor with last branch record (LBR) support
>> >
>> > Is it really a requirement or will it only make profiles more accurate?
>>
>> It's optional, updated the doc.
>
> Can you give an example on how this is supposed to work on non Intel
> CPUs? It is not obvious to me.
>
> --
> Markus


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]