From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id Oa/ABKPN8F8ubQAAWB0awg (envelope-from ) for ; Sat, 02 Jan 2021 14:46:43 -0500 Received: by simark.ca (Postfix, from userid 112) id 04A881F0AA; Sat, 2 Jan 2021 14:46:43 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [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 6BFB51E99A for ; Sat, 2 Jan 2021 14:46:41 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 254A3386F46A; Sat, 2 Jan 2021 19:46:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 254A3386F46A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1609616800; bh=GZtc37ZTrPIjWarBCHMjuGRjGIjYLbmQnCINeusu+28=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=t8gz3oMOTJ6FZkrSjrvrCnB83aGNoMVMXWg4hzxRKyp7Xv/cgdkE4HVLhrHeTa2Ur BHWzsaznQVFE8g7xPRK4PcERJkrxMowdUWOJGLRIH5WpVCC9sVYpIEoy2qT4tjVuiz r2eNgvoIaDvyrKAfVlXnwtnk4XF7Oe3cttBRqr70= Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) by sourceware.org (Postfix) with ESMTPS id D0E62386F442; Sat, 2 Jan 2021 19:46:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D0E62386F442 Received: by mail-oi1-x22c.google.com with SMTP id d203so27549437oia.0; Sat, 02 Jan 2021 11:46:36 -0800 (PST) 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=GZtc37ZTrPIjWarBCHMjuGRjGIjYLbmQnCINeusu+28=; b=EkLMDhJqw1H9M78chr+98g7dzr4qhoTk/CijZDxfdWsLAd2YQmu7axqP7sJ8xYnQJ+ n8u752XnR4uuocigfEP0o8JI25w3vPMKXyd5CdjjuhJ5XkgjMpL3epJajsG9YFzBxfir JvQRORskySBwIUL3yf+QftbiZwS9Qj9LO3M2BeO2hgD8K18HuGR0hIjArxvmZw7oV2Br oY848Y4YO01ndu7jY4RgTdGQe9NGjH2x1DYQZCAi6wnIjpJDcbO9xE1MQgc+Mbgw4CmH 5z6tqr8l+nzighPYADMXqq5sMTX9l8nac2lKa/QTZWQKDvcE6W7+KgV8catO/3wrFxvs hdIQ== X-Gm-Message-State: AOAM533UYY17QtNgusrCRmiuoeg9q7IGgFpV/tizloAXEhxOxuBci6TP T708C2Ow58VqtpZt2To66LgrM6lfMWmaqOnCSE59HlI3ASw= X-Google-Smtp-Source: ABdhPJwKkkYJCCFX9KI9wtLPfzyVuyMlZAFBzEBlkdY/XmQrLO308qCZ0Vwal4CNBJywDDPn6B8rNyXE7v8cJL2v2B8= X-Received: by 2002:aca:f5d3:: with SMTP id t202mr13894933oih.25.1609616796287; Sat, 02 Jan 2021 11:46:36 -0800 (PST) MIME-Version: 1.0 References: <20201219181036.178248-1-hjl.tools@gmail.com> <20210102192222.GA30983@gate.crashing.org> In-Reply-To: <20210102192222.GA30983@gate.crashing.org> Date: Sat, 2 Jan 2021 11:46:00 -0800 Message-ID: Subject: Re: V3 [PATCH 0/5] Support the PGO build for binutils+gdb To: Segher Boessenkool Content-Type: text/plain; charset="UTF-8" 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: , From: "H.J. Lu via Gdb-patches" Reply-To: "H.J. Lu" Cc: Matthias Klose , GCC Patches , Binutils , GDB Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" On Sat, Jan 2, 2021 at 11:24 AM Segher Boessenkool wrote: > > 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 --with-build-config= is more or less for bootstrapping GCC. In case of binutils, we don't build GCC. We only train GCC with binutils/GDB testsuites. -- H.J.