From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id uz3wHazI8F+PbAAAWB0awg (envelope-from ) for ; Sat, 02 Jan 2021 14:25:32 -0500 Received: by simark.ca (Postfix, from userid 112) id 6C1761F0AA; Sat, 2 Jan 2021 14:25:32 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=0.3 required=5.0 tests=MAILING_LIST_MULTI,RDNS_NONE autolearn=no autolearn_force=no version=3.4.2 Received: from sourceware.org (unknown [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id BA1731E552 for ; Sat, 2 Jan 2021 14:25:30 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 359E1386F438; Sat, 2 Jan 2021 19:25:30 +0000 (GMT) Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) by sourceware.org (Postfix) with ESMTP id E5CA73858024; Sat, 2 Jan 2021 19:25:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E5CA73858024 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=kernel.crashing.org Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=segher@kernel.crashing.org Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id 102JMNal031229; Sat, 2 Jan 2021 13:22:23 -0600 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id 102JMMDL031227; Sat, 2 Jan 2021 13:22:22 -0600 X-Authentication-Warning: gate.crashing.org: segher set sender to segher@kernel.crashing.org using -f Date: Sat, 2 Jan 2021 13:22:22 -0600 From: Segher Boessenkool To: "H.J. Lu" Subject: Re: V3 [PATCH 0/5] Support the PGO build for binutils+gdb Message-ID: <20210102192222.GA30983@gate.crashing.org> References: <20201219181036.178248-1-hjl.tools@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201219181036.178248-1-hjl.tools@gmail.com> User-Agent: Mutt/1.4.2.3i X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Matthias Klose , gcc-patches@gcc.gnu.org, binutils@sourceware.org, gdb-patches@sourceware.org Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" On Sat, Dec 19, 2020 at 10:10:31AM -0800, H.J. Lu via Gcc-patches wrote: > Add the --enable-pgo-build[=lto] configure option. When binutils+gdb > is not built together with GCC, --enable-pgo-build enables the PGO build: > > 1. First build with -fprofile-generate. > 2. Use "make maybe-check-*" to generate profiling data and pass -i to make > to ignore errors when generating profiling data. > 3. Use "make clean" to remove the previous build. > 4. Rebuild with -fprofile-use. Can this not use --with-build-config=? As the user interface I mean, you probably still need most of this code, but at least it will be more obvious how to handle conflicts in user-specified options. Segher