From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) by sourceware.org (Postfix) with ESMTPS id EA86C3857807 for ; Mon, 10 May 2021 23:46:52 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org EA86C3857807 Received: by mail-lj1-x235.google.com with SMTP id c15so8371612ljr.7 for ; Mon, 10 May 2021 16:46:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=K2gwh8MYopZJJmoo5gHBg2BO7RH/ETPVC1CoR6S50Fw=; b=IkzJU8X+Pc77cXRmBkY8iG/+44VIP1TznlmvdKlw2J8ghnBw018SBHo9c8kg5MgyhC qjGRzRlDxYbzvLZqyfz79amt3rZu1bA6yahbZf3KJ5C6hNCAlisgfm78MQYzAY98d3FN yWITiY6aY7xJG69/WIsM3UCQixa8kEUjcGsJibktswfalII9lLjUyMS9OBDT8Kh6v2KZ sefOk59B6jMJ2Rj1/lxFzABkiRaIjDyfKHQH5+LWNJ4cNmC4vQks4PTwqf8C7snYIvLs lW2aa10e8o+UFLiW8HD8Me9RdCZOFbNq21cg5055/tnWoU4dpl+f1iD7cogTtBb/MfRs 40YQ== X-Gm-Message-State: AOAM531je/dssoLvIjEMhc52kak8DDjITCBCUSnTuoPzW4J5yttWZUz8 Y+EqChouIxXaQdj4H5l5itJ472F0SYTjkr9bHvVm1A== X-Google-Smtp-Source: ABdhPJyev/XbJZVYWlN38K/xWapypS6+LbVCxh+re/L80iYDY4JSKfjeXKor3KVgyzU08s95jAormGG/o8EB1JkrklU= X-Received: by 2002:a05:651c:2002:: with SMTP id s2mr22531537ljo.477.1620690411437; Mon, 10 May 2021 16:46:51 -0700 (PDT) MIME-Version: 1.0 References: <20210423192834.GA1949@kam.mff.cuni.cz> <20210425190754.GA88857@kam.mff.cuni.cz> <87a6plulkz.fsf@linux.intel.com> <20210426180011.GA1401198@tassilo.jf.intel.com> <20210429054025.GB4032392@tassilo.jf.intel.com> In-Reply-To: <20210429054025.GB4032392@tassilo.jf.intel.com> From: Wei Mi Date: Mon, 10 May 2021 16:46:39 -0700 Message-ID: Subject: Re: State of AutoFDO in GCC To: Andi Kleen Cc: Hongtao Yu , Xinliang David Li , Jan Hubicka , "gcc@gcc.gnu.org" , Eugene Rozenfeld , Wenlei He X-Spam-Status: No, score=-17.7 required=5.0 tests=BAYES_00, DKIMWL_WL_MED, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, USER_IN_DEF_DKIM_WL, USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2021 23:46:56 -0000 https://github.com/google/autofdo has been updated. Now create_gcov/dump_gcov are added back and can be built separately. Please look at "2.2 Build autofdo tool for gcc" in https://github.com/google/autofdo#readme On Wed, Apr 28, 2021 at 10:40 PM Andi Kleen wrote: > > On Mon, Apr 26, 2021 at 06:40:56PM +0000, Hongtao Yu wrote: > > Andi, thanks for pointing out the perf script issues. Can you please > > elaborate a bit on the exact issue you have seen? We=E2=80=99ve been= using > > specific output of perf script such as mmap, LBR and callstack event= s > > filtered by process id. It works fine so far but may certainly hit issues > > in the future with extended uses. > > Okay I took a look at the latest autofdo now. It seems to be basically > a LLVM project now that depends on LLVM to even build with all kinds > of dependency hell on some old LLVM version and other packages. > > I guess gcc will really need a replacement that doesn't pull in > all of LLVM if it wants to continue supporting autofdo. > > I'm myself unable to build now. > > I'm using the old version I had a git fork of and that > was before all of this. I added a patch to make it work > with the latest perf by ignoring increased perf_attr > and unknown perf events. > > Honza please use > > https://github.com/andikleen/autofdo -b perf-future > > for testing. > > -Andi >