State of AutoFDO in GCC

GCC documentation for AutoFDO points to create_gcov tool that converts perf.data file into gcov format that can be consumed by gcc with -fauto-profile (https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html, https://gcc.gnu.org/wiki/AutoFDO/Tutorial). I noticed that the source code for create

RE: [EXTERNAL] Re: State of AutoFDO in GCC

involve too much effort. David Having the tool third-party makes keeping the whole chain working more difficult. Richard. > Thanks, > > David > > On Thu, Apr 22, 2021 at 3:29 PM Jan Hubicka > mailto:hubi...@ucw.cz>> wrote: > > > > On 4/22/21 9:58 PM, Eugen

RE: [EXTERNAL] Re: State of AutoFDO in GCC

I tried following the instructions in "2.2 Build autofdo tool for gcc" in https://github.com/google/autofdo#readme and got build failures: eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja [1/228] Building CXX object CMakeFiles/create_gcov_lib.dir/profile.cc.o FAILED: CMakeFiles/create_gcov_l

RE: [EXTERNAL] Re: State of AutoFDO in GCC

Thank you Wei. Looks like something is still missing. This time perf_data.pb.h is not found. I'm getting the error below (on Ubuntu 18.04 with cmake 3.12.1): eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja [1/241] Building CXX object CMakeFiles/dump_gcov_lib.dir/profile.cc.o FAILED: CMakeFi

RE: [EXTERNAL] Re: State of AutoFDO in GCC

That fixed the error I saw before but the build still fails. The errors start with eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja [2/217] Building CXX object CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/huge_page_deducer.cc.o FAILED: CMakeFiles/quipper_perf.dir

RE: [EXTERNAL] Re: State of AutoFDO in GCC

That eliminates the previous error but there is a new one: eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja [3/199] Building CXX object CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/perf_reader.cc.o FAILED: CMakeFiles/quipper_perf.dir/third_party/perf_data_converte

RE: [EXTERNAL] Re: State of AutoFDO in GCC

Both are 3.0.0-9.1ubuntu1: eugene@eugene-Virtual-Machine:~/autofdo1/build$ apt list protobuf-compiler Listing... Done protobuf-compiler/bionic,now 3.0.0-9.1ubuntu1 amd64 [installed] eugene@eugene-Virtual-Machine:~/autofdo1/build$ apt list libprotobuf-dev Listing... Done libprotobuf-dev/bionic,now

RE: [EXTERNAL] Re: State of AutoFDO in GCC

3.0.0 is the latest supported version on Ubuntu 18.04. I verified that the build works on Ubuntu 20.04 with protobuf-compiler and libprotobuf-dev version 3.6.1.3. Eugene -Original Message- From: Wei Mi Sent: Tuesday, May 25, 2021 8:07 PM To: Eugene Rozenfeld Cc: Andi Kleen ; Hongtao

RE: [EXTERNAL] Re: State of AutoFDO in GCC

It appears that create_gcov doesn't support binaries with dwarf version 5 (which is the current default). I tried a trivial example and got reasonable gcov files for binaries with dwarf v2, v3, and v4 but the same example with dwarf v5 produced "File './sort' has mangled .debug_info section." a

RE: [EXTERNAL] Re: State of AutoFDO in GCC

this. The version of perf I'm using is 5.8.18. Thanks, Eugene -Original Message- From: Andi Kleen Sent: Friday, April 30, 2021 2:46 PM To: Eugene Rozenfeld via Gcc Cc: Xinliang David Li ; Richard Biener ; Eugene Rozenfeld ; Jan Hubicka Subject: Re: [EXTERNAL] Re: State of AutoF

Reporting lto bugs

I ran into a bug with lto: no line number info gets emitted when building my project with -flto and -g (with gcc 8.2). I'd like to provide a repro in the bug report but I don't know if there is an easy way to collect everything. The instructions at https://gcc.gnu.org/bugs/ seem to cover non-lto

RE: [EXTERNAL] Re: Reporting lto bugs

Eugene Rozenfeld Cc: gcc@gcc.gnu.org Subject: [EXTERNAL] Re: Reporting lto bugs On Fri, Sep 24, 2021 at 3:45 AM Eugene Rozenfeld via Gcc wrote: > > I ran into a bug with lto: no line number info gets emitted when building my > project with -flto and -g (with gcc 8.2). I'd like to p

Re: State of AutoFDO in GCC

Hello GCC community. I started this thread on the state of AutoFDO in GCC more than a year ago. Here is the first message in the thread: https://gcc.gnu.org/pipermail/gcc/2021-April/235860.html Since then I committed a number of patches to revive AutoFDO in GCC: Fix a typo in an AutoFDO error

RE: [EXTERNAL] Re: State of AutoFDO in GCC

m. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] On Tue, Jul 26, 2022 at 4:13 PM Eugene Rozenfeld via Gcc wrote: > > Hello GCC community. > > I started this thread on the state of AutoFDO in GCC more than a year > ago. Here is the first mess

RE: [EXTERNAL] Re: State of AutoFDO in GCC

From: Jan Hubicka Sent: Wednesday, July 27, 2022 12:27 AM To: David Edelsohn Cc: Eugene Rozenfeld ; Martin Liska ; Xinliang David Li ; gcc ; Andi Kleen ; Joseph Myers Subject: [EXTERNAL] Re: State of AutoFDO in GCC > On Tue, Jul 26, 2022 at 4:13 PM Eugene Rozenfeld via Gcc > wrot

RE: [EXTERNAL] Re: State of AutoFDO in GCC

nt at https://aka.ms/LearnAboutSenderIdentification ] On 2022/7/27 09:31, Xionghu Luo wrote: > > > On 2022/7/27 04:12, Eugene Rozenfeld via Gcc wrote: >> Hello GCC community. >> >> I started this thread on the state of AutoFDO in GCC more than a year >> ago. Here

AutoFDO tools for GCC

Hello, I've been the AutoFDO maintainer for the last 1.5 years. I've resurrected autoprofiledbootstrap build and made a number of other fixes/improvements (e.g., discriminator support). The tools for AutoFDO (create_gcov, etc.) currently live in https://github.com/google/AutoFDO repo and GCC