From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 3A6FD385E445 for ; Wed, 27 Mar 2024 20:49:55 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 3A6FD385E445 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 3A6FD385E445 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.133.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1711572598; cv=none; b=WRPqx4Wu/j5xplWxNeRz5u/wAgH6UMNcNTOkwwFeEH3trGOvVKQKzaEDu6XNAOTdx4Ivla7bjb+iw6wDlCjWAWdFLGjiHkrGOMcvHUbxpUSSt4OmatyqU8JN6gxWCZie49M1inaRwmUbDy0p9tU0N+1/x9q0/BM+GnTtizMesyQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1711572598; c=relaxed/simple; bh=Ny8cjxONkWrOaJIckK1PLCLAktMOGi6JScDJ3wOVE7U=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=pT63svYo39+0ZxLrbcVDFaUGwWXuU0OP5FHzk97J4e9KX1HaYSIY+f04myxuWgJ15JARJeqmabwms0XPv+dUt4HDi3a9fuDqfHzLOh0WVVDqvfjUKLTdVvoCFDWqzvnZA1qI4KP58ms61D0pA3RTa0IMxlVzqTYSjDsbdO0voxI= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1711572594; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WR8SXOJSOQqOulayIQQAFx146j/UM1xa7o5BwESwcFk=; b=PkZpU9bwO9uEOi2gPOi8gr3/GdvOOmTAQM41hGim5vk3aZqqkWFmjNADUUt0Ryx+sLcDos aqizkNd8IGeQrwEV+DBdI0PBTE4xf0X6WoSXrV7vpoP8mwQNDFLeNVWEIhWA04cummc+tA tUsTHkTymINsQu9rLIjmhiEGZWllKGs= Received: from mail-io1-f69.google.com (mail-io1-f69.google.com [209.85.166.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-570-jl3Kp3qfPDuSBSwyGPZqNw-1; Wed, 27 Mar 2024 16:49:53 -0400 X-MC-Unique: jl3Kp3qfPDuSBSwyGPZqNw-1 Received: by mail-io1-f69.google.com with SMTP id ca18e2360f4ac-7cbf1aea97fso26683739f.2 for ; Wed, 27 Mar 2024 13:49:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711572592; x=1712177392; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=WR8SXOJSOQqOulayIQQAFx146j/UM1xa7o5BwESwcFk=; b=QPghpDE15bxEPvflkXfvwn/H9ZwWEg1wMsRMh1E9pf/6t27AIwMQEnpff43bcP5xzP zSEk4995U5itjbYOxiysHULiY/8lg/QkWumdlajxkbesjtBaj1q68EGZv9UGckHD/P3j g13EVCdFtINx16ehgYzsbwmOCNXw6zj8Eyldq7wEbL0rWog7hLRatb0ov0/oURKmzEvw 9V5C1PH3Ha0NgSkoxgf70tB1dGchyxcjRUfXRsPbIfOs7o5qae4CZLS2K5XxU3Pychz8 vtjUQXgvtY9uFkpRmKYClpS2X47w2+GyE5k5ESiz4+6dL+rbMCmxgrIfyP4NDcv8wLEo k1zw== X-Forwarded-Encrypted: i=1; AJvYcCXIvUsih4mHzKn0Y226typYVjVEcDyUp6sVak9Men5Yr8CxfHWy60hhOfod9wjKPCw0vVbvMyK3ISzr0W5+FSw= X-Gm-Message-State: AOJu0YzrBhY309utzgxzQZSqz9m38pP8auOrRtk550gcOHVz1yI0G2T5 fuAUYUY+cJv112XrkH8jAGJEDtou5IIz3MES2f+g3WW7R722KKpmthYai1z8B9EiPmabKFM88Mt DyqZMa7gr9/4Mvsr5M+xtyNpnG8fYXnxHQQ86wyvAc4SX2XaZnJvEFjRGay/pJJwU5eEFKXTp1V sNQTtyqVinvmEV6T0id1w= X-Received: by 2002:a05:6602:1786:b0:7d0:3d14:94be with SMTP id y6-20020a056602178600b007d03d1494bemr1263259iox.12.1711572592301; Wed, 27 Mar 2024 13:49:52 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFCRqxjAl8aFf5K+d6Ecj0KFeKCnBflSHlGrthJN/+zc5PMxnnEKXuB6yhJ7tOnF6emACIwQM+b1N5Phfnv2DY= X-Received: by 2002:a05:6602:1786:b0:7d0:3d14:94be with SMTP id y6-20020a056602178600b007d03d1494bemr1263250iox.12.1711572592075; Wed, 27 Mar 2024 13:49:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jason Merrill Date: Wed, 27 Mar 2024 16:49:40 -0400 Message-ID: Subject: Re: AutoFDO tools for GCC To: Andi Kleen Cc: Richard Biener , Eugene Rozenfeld , "gcc@gcc.gnu.org" , Snehasish Kumar , Jan Hubicka X-Mimecast-Spam-Score: 1 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-6.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Tue, Mar 26, 2024 at 6:41=E2=80=AFPM Andi Kleen via Gcc wrote: > > On Tue, Mar 26, 2024 at 08:45:22AM +0100, Richard Biener wrote: > > On Mon, Mar 25, 2024 at 9:54=E2=80=AFPM Eugene Rozenfeld via Gcc > > wrote: > > > > > > Hello, > > > > > > I've been the AutoFDO maintainer for the last 1.5 years. I've resurre= cted autoprofiledbootstrap build and made a number of other fixes/improveme= nts (e.g., discriminator support). > > > > > > The tools for AutoFDO (create_gcov, etc.) currently live in https://g= ithub.com/google/AutoFDO repo and GCC AutoFDO documentation points users t= o that repo. That repo also has tools for LLVM AutoFDO. > > > https://github.com/google/AutoFDO has several submodules: https://gi= thub.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 fin= d 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 G= CC 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. > > > > I think it makes sense for GCC specific parts to live in the GCC > > repository alongside gcov tools. I do wonder how much common code > > there is > > between the LLVM and the GCC tooling though and whether it makes sense > > to keep it common (and working with both frontends)? The > > pragmatic solution would have been to fork the repo on github to a > > place not within the google group ... > > In tree would need convincing Google to assign the copyright. Would it? Looks like it's under a free license (apache 2), not everything in the tree is copyright FSF or GPL3. Jason