From: Filip Kastl <fkastl@suse.cz>
To: Thomas Schwinge <tschwinge@baylibre.com>,
Martin Jambor <mjambor@suse.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: [PATCH] contrib/check-params-in-docs.py: Ignore target-specific params
Date: Fri, 12 Apr 2024 09:08:13 +0200 [thread overview]
Message-ID: <Zhjd3RG3cqKsKteb@localhost.localdomain> (raw)
In-Reply-To: <87le5jenqs.fsf@euler.schwinge.ddns.net>
On Thu 2024-04-11 20:51:55, Thomas Schwinge wrote:
> Hi!
>
> On 2024-04-11T19:52:51+0200, Martin Jambor <mjambor@suse.cz> wrote:
> > contrib/check-params-in-docs.py is a script that checks that all
> > options reported with ./gcc/xgcc -Bgcc --help=param are in
> > gcc/doc/invoke.texi and vice versa.
>
> Eh, first time I'm hearing about this one!
>
> (a) Shouldn't this be running as part of the GCC build process?
>
> > gcn-preferred-vectorization-factor is in the manual but normally not
> > reported by --help, probably because I do not have gcn offload
> > configured.
>
> No, because you've not been building GCC for GCN target. ;-P
>
> > This patch makes the script silently about this particular
> > fact.
>
> (b) Shouldn't we instead ignore any '--param's with "gcn" prefix, similar
> to how that's done for "skip aarch64 params"?
>
> (c) ..., and shouldn't we likewise skip any "x86" ones?
>
> (d) ..., or in fact any target specific ones, following after the generic
> section? (Easily achieved with a special marker in
> 'gcc/doc/invoke.texi', just before:
>
> The following choices of @var{name} are available on AArch64 targets:
>
> ..., and adjusting the 'takewhile' in 'contrib/check-params-in-docs.py'
> accordingly?
Hi,
I've made a patch to address (b), (c), (d). I didn't adjust takewhile. I
chose to do it differently since target-specific params in both invoke.texi and
--help=params have to be ignored.
The downside of this patch is that the script won't complain if someone adds a
target-specific param and doesn't document it.
What do you think?
Cheers,
Filip
-- 8< --
contrib/check-params-in-docs.py is a script that checks that all options
reported with gcc --help=params are in gcc/doc/invoke.texi and vice
versa.
gcc/doc/invoke.texi lists target-specific params but gcc --help=params
doesn't. This meant that the script would mistakenly complain about
parms missing from --help=params. Previously, the script was just set
to ignore aarch64 and gcn params which solved this issue only for x86.
This patch sets the script to ignore all target-specific params.
contrib/ChangeLog:
* check-params-in-docs.py: Ignore target specific params.
Signed-off-by: Filip Kastl <fkastl@suse.cz>
---
contrib/check-params-in-docs.py | 21 +++++++++++++--------
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/contrib/check-params-in-docs.py b/contrib/check-params-in-docs.py
index f7879dd8e08..ccdb8d72169 100755
--- a/contrib/check-params-in-docs.py
+++ b/contrib/check-params-in-docs.py
@@ -38,6 +38,9 @@ def get_param_tuple(line):
description = line[i:].strip()
return (name, description)
+def target_specific(param):
+ return param.split('-')[0] in ('aarch64', 'gcn', 'x86')
+
parser = argparse.ArgumentParser()
parser.add_argument('texi_file')
@@ -45,13 +48,16 @@ parser.add_argument('params_output')
args = parser.parse_args()
-ignored = {'logical-op-non-short-circuit', 'gcn-preferred-vectorization-factor'}
-params = {}
+ignored = {'logical-op-non-short-circuit'}
+help_params = {}
for line in open(args.params_output).readlines():
if line.startswith(' ' * 2) and not line.startswith(' ' * 8):
r = get_param_tuple(line)
- params[r[0]] = r[1]
+ help_params[r[0]] = r[1]
+
+# Skip target-specific params
+help_params = [x for x in help_params.keys() if not target_specific(x)]
# Find section in .texi manual with parameters
texi = ([x.strip() for x in open(args.texi_file).readlines()])
@@ -66,14 +72,13 @@ for line in texi:
texi_params.append(line[len(token):])
break
-# skip digits
+# Skip digits
texi_params = [x for x in texi_params if not x[0].isdigit()]
-# skip aarch64 params
-texi_params = [x for x in texi_params if not x.startswith('aarch64')]
-sorted_params = sorted(texi_params)
+# Skip target-specific params
+texi_params = [x for x in texi_params if not target_specific(x)]
texi_set = set(texi_params) - ignored
-params_set = set(params.keys()) - ignored
+params_set = set(help_params) - ignored
success = True
extra = texi_set - params_set
--
2.43.1
next prev parent reply other threads:[~2024-04-12 7:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 15:54 [committed] amdgcn: Prefer V32 on RDNA devices Andrew Stubbs
2024-03-28 7:00 ` Thomas Schwinge
2024-04-08 10:45 ` GCN: '--param=gcn-preferred-vector-lane-width=[default,32,64]' (was: [committed] amdgcn: Prefer V32 on RDNA devices) Thomas Schwinge
2024-04-08 12:24 ` GCN: '--param=gcn-preferred-vector-lane-width=[default,32,64]' Andrew Stubbs
2024-04-08 20:17 ` GCN: '--param=gcn-preferred-vectorization-factor=[default,32,64]' (was: GCN: '--param=gcn-preferred-vector-lane-width=[default,32,64]') Thomas Schwinge
2024-04-11 17:52 ` [PATCH] contrib/check-params-in-docs.py: Ignore gcn-preferred-vectorization-factor Martin Jambor
2024-04-11 18:51 ` Thomas Schwinge
2024-04-12 7:08 ` Filip Kastl [this message]
2024-04-12 7:40 ` [PATCH] contrib/check-params-in-docs.py: Ignore target-specific params Thomas Schwinge
2024-04-12 8:39 ` Martin Jambor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zhjd3RG3cqKsKteb@localhost.localdomain \
--to=fkastl@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=mjambor@suse.cz \
--cc=tschwinge@baylibre.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).