public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eugene Rozenfeld <Eugene.Rozenfeld@microsoft.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Cc: Snehasish Kumar <snehasishk@google.com>,
	Andi Kleen <ak@linux.intel.com>, Jan Hubicka <hubicka@ucw.cz>
Subject: AutoFDO tools for GCC
Date: Mon, 25 Mar 2024 20:52:40 +0000	[thread overview]
Message-ID: <CO1PR21MB13313861B281B3878D031FEF91362@CO1PR21MB1331.namprd21.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

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 AutoFDO documentation points users to that repo. That repo also has tools for LLVM AutoFDO.
https://github.com/google/AutoFDO  has several submodules: https://github.com/google/autofdo/blob/master/.gitmodules

I got a message from Snehasish (cc'd) that google intends to migrate the tools for LLVM to the LLVM repo and wants to archive https://github.com/google/AutoFDO. That will be a problem for AutoFDO in GCC. The idea to find a different home for GCC AutoFDO tools was discussed before on this alias but this becomes more urgent now. One idea was to build these tools from GCC repo and another was to produce gcov from perf tool directly. Andi (cc'd)  had some early unfinished prototype for latter.

Please let me know if you have thoughts on how we should proceed.

Thanks,

Eugene

             reply	other threads:[~2024-03-25 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 20:52 Eugene Rozenfeld [this message]
2024-03-26  7:45 ` Richard Biener
2024-03-26 22:39   ` Andi Kleen
2024-03-27 20:49     ` Jason Merrill
2024-04-02 22:30       ` Snehasish Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CO1PR21MB13313861B281B3878D031FEF91362@CO1PR21MB1331.namprd21.prod.outlook.com \
    --to=eugene.rozenfeld@microsoft.com \
    --cc=ak@linux.intel.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=snehasishk@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).