From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hamza.pair.com (hamza.pair.com [209.68.5.143]) by sourceware.org (Postfix) with ESMTPS id 0BCB03858D33 for ; Fri, 17 Feb 2023 00:42:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0BCB03858D33 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=pfeifer.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=pfeifer.com Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com (Postfix) with ESMTP id 070D233E6B for ; Thu, 16 Feb 2023 19:42:36 -0500 (EST) Received: from [192.168.1.80] (188-23-63-229.adsl.highway.telekom.at [188.23.63.229]) (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 hamza.pair.com (Postfix) with ESMTPSA id 9594F33EAD for ; Thu, 16 Feb 2023 19:42:35 -0500 (EST) Date: Fri, 17 Feb 2023 01:42:34 +0100 (CET) From: Gerald Pfeifer To: gcc-patches@gcc.gnu.org Subject: [pushed] doc: Reword how to get possible values of a parameter (was: Document all param values and remove defaults (PR middle-end/86078)) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323328-1363286237-1676594555=:19920" X-Scanned-By: mailmunge 3.10 on 209.68.5.143 Message-Id: <20230217004236.070D233E6B@hamza.pair.com> X-Spam-Status: No, score=-9.3 required=5.0 tests=BAYES_00,GIT_PATCH_0,KAM_DMARC_STATUS,RCVD_IN_BARRACUDACENTRAL,SPF_HELO_NONE,SPF_PASS,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: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-1363286237-1676594555=:19920 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT On Mon, 24 Sep 2018, Martin Li¨ka wrote: > As mentioned in the PR we miss defaults for quite some param option. > I agreed with Richi that easiest way how to fix that would be to remove > that from documentation and use rather --help=param. It's done in the > patch. And here is a little follow-up patch after that, ahem, little while... Pushed. Gerald gcc/ChangeLog: * doc/invoke.texi (Optimize Options): Reword the explanation getting minimal, maximal and default values of a parameter. --- gcc/doc/invoke.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index 6def1fd631e..7b308cd3c31 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -14678,8 +14678,8 @@ The names of specific parameters, and the meaning of the values, are tied to the internals of the compiler, and are subject to change without notice in future releases. -In order to get minimal, maximal and default value of a parameter, -one can use @option{--help=param -Q} options. +In order to get the minimal, maximal and default values of a parameter, +use the @option{--help=param -Q} options. In each case, the @var{value} is an integer. The following choices of @var{name} are recognized for all targets: -- 2.39.1 --8323328-1363286237-1676594555=:19920--