Re: Re: State of AutoFDO in GCC

2021-05-08 Thread 172060045
> > Hi all, 
> >
> > I`m using GCC 9.3 AutoFDO and the old version create_gcov on arm64 
> > and it works well. Actually it support not only LBR like mode but 
> > also inst_retired even cycles event, which`s the early implementation 
> > of AutoFDO[1]. There is no difference in output format of create_gcov 
> > between LBR mode and inst_retired. inst_retired is less accurate than 
> > LBR but still works.
> >
> > I hope AutoFDO could work better on GCC and am willing to contribute 
> > to it, does anybody have suggestions for me?
> 
> I think at a minimum we need someone to run the test suite regularly
> and look at all the problem, at least filling PRs, so that regressions
> could be fixed.
> 
> But I actually hope one of the automatic testers could at least do
> the testing.
> 

Hi Andi,
Thanks for your advice, I'm trying to start these jobs.

-Yancheng

> And perhaps try it on real applications and see how much you can
> improve performance, and if there are problems also file PRs.
> 

With my tests, AutoFDO could achieve almost half of the effect of 
instrumentation FDO on real applications such as MySQL 8.0.20 .

> There's some other work that could be done (e.g. port some of the
> missing changes from the old google autofdo tree to mainline), but that
> might be more difficult depending on your gcc internals expertise.
> 

get it, thanks.

> -Andi


gcc-11-20210508 is now available

2021-05-08 Thread GCC Administrator via Gcc
Snapshot gcc-11-20210508 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/11-20210508/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch 
releases/gcc-11 revision 99964f67bab3cc1ddac51b470e7f1b616a537348

You'll find:

 gcc-11-20210508.tar.xz   Complete GCC

  SHA256=b234e6ea1bf8a4a0bf066901bdb6c060d9c13df21ecd76a9b5c9e8ea513abe95
  SHA1=bd833cfd6a03295f6ad55b423583d463f7fb5cf3

Diffs from 11-20210501 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-11
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.