Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH] [pre-commit] Add tclint hook
Date: Mon, 15 Sep 2025 10:41:05 +0200	[thread overview]
Message-ID: <20250915084105.23171-1-tdevries@suse.de> (raw)

Add a pre-commit hook that enables tclint [1] (a Tcl linter) for the gdb
testsuite.

The pre-commit hook doesn't reference the official url, because that one
doesn't have pre-commit support yet [2].

Instead, it uses a fork on my personal github account.  The fork contains a
tag v0.6.0-gdb, which is the official v0.6.0 release plus a commit adding a
.pre-commit-hooks.yaml file.  Given that this is a personal github account, I
thought it would be safer to refer to the git SHA than to the tag.

Also add a tclint configuration file gdb/testsuite/tclint.toml.

In the configuration file, we still ignore most dirs because they're not
tclint-clean.

Consequently, the tclint pre-commit check passes:
...
$ pre-commit run --all-files -v tclint
tclint........................Passed
- hook id: tclint
- duration: 0.25s
$
...

PR testsuite/33403
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33403

[1] https://github.com/nmoroze/tclint
[2] https://github.com/nmoroze/tclint/issues/110
---
 .pre-commit-config.yaml   | 15 ++++++++
 gdb/testsuite/tclint.toml | 75 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 90 insertions(+)
 create mode 100644 gdb/testsuite/tclint.toml

diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index a4a8a5fa1ef..6bbd51fb6d0 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -88,3 +88,18 @@ repos:
       verbose: true
       always_run: true
       stages: [commit-msg]
+  - # We'd like to use the official repo, like this:
+    #   repo: https://github.com/nmoroze/tclint
+    #   rev: v0.6.0
+    # but it doesn't have a .pre-commit-hooks.yaml file.
+    # Work around this by using an unoffical repo.  The repo contains a tag
+    # v0.6.0-gdb that adds a .pre-commit-hooks.yaml file to the v0.6.0 release
+    # of the offical repo.  Since we're using an unofficial repo, use the git
+    # SHA instead of the tag.
+    repo: https://github.com/vries/tclint.git
+    rev: 2e6b4510fb3d3d6f8f2609af0f7158fabc0c96e4
+    hooks:
+    - id: tclint
+      args: [--config, gdb/testsuite/tclint.toml]
+      types_or: [file]
+      files: 'gdb/testsuite/.*\.(exp|tcl)$'
diff --git a/gdb/testsuite/tclint.toml b/gdb/testsuite/tclint.toml
new file mode 100644
index 00000000000..c30fc210d63
--- /dev/null
+++ b/gdb/testsuite/tclint.toml
@@ -0,0 +1,75 @@
+# Copyright 2025 Free Software Foundation, Inc.
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+# Configuration file for tclint ( https://github.com/nmoroze/tclint ).
+
+exclude = [
+"gdb/testsuite/boards",
+"gdb/testsuite/config",
+"gdb/testsuite/lib",
+"gdb/testsuite/gdb.ada",
+"gdb/testsuite/gdb.arch",
+"gdb/testsuite/gdb.asm",
+"gdb/testsuite/gdb.base",
+"gdb/testsuite/gdb.btrace",
+"gdb/testsuite/gdb.compile",
+"gdb/testsuite/gdb.cp",
+"gdb/testsuite/gdb.ctf",
+"gdb/testsuite/gdb.dap",
+"gdb/testsuite/gdb.debuginfod",
+"gdb/testsuite/gdb.disasm",
+"gdb/testsuite/gdb.dlang",
+"gdb/testsuite/gdb.dwarf2",
+"gdb/testsuite/gdb.fortran",
+"gdb/testsuite/gdb.gdb",
+"gdb/testsuite/gdb.go",
+"gdb/testsuite/gdb.guile",
+"gdb/testsuite/gdb.linespec",
+"gdb/testsuite/gdb.mi",
+"gdb/testsuite/gdb.multi",
+"gdb/testsuite/gdb.opencl",
+"gdb/testsuite/gdb.perf",
+"gdb/testsuite/gdb.python",
+"gdb/testsuite/gdb.reverse",
+"gdb/testsuite/gdb.rocm",
+"gdb/testsuite/gdb.server",
+"gdb/testsuite/gdb.stabs",
+"gdb/testsuite/gdb.threads",
+"gdb/testsuite/gdb.trace",
+]
+
+# A maximum line length of 80 is current policy, but hasn't been too strictly
+# enforced.  It's the most frequent and least harmful violation.
+# Ignore this for now.
+ignore = ["line-length"]
+
+extensions = ["exp", "tcl"]
+
+[style]
+# Used by tclfmt.  Doesn't support mixed TAB and spaces style we use. See
+# this tclint issue ( https://github.com/nmoroze/tclint/issues/109 ).
+indent = 4
+
+# Used by both tclint and tclfmt.  Current policy is 80.
+line-length = 80
+
+# Used by tclfmt.
+max-blank-lines = 1
+
+# Used by tclfmt.  False conflicts with emacs tcl mode.
+indent-namespace-eval = true
+
+# Used by tclfmt.
+spaces-in-braces = false

base-commit: 6affec82bd4186aaf2e6733425b1e05870fc0582
-- 
2.51.0


             reply	other threads:[~2025-09-15  8:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15  8:41 Tom de Vries [this message]
2025-09-17 15:42 ` Tom Tromey
2025-09-17 18:15   ` Tom de Vries
2025-09-17 18:35     ` Tom Tromey
2025-09-17 19:08       ` Tom de Vries
2025-09-17 19:43         ` Tom de Vries
2025-09-18  0:22           ` Tom Tromey
2025-09-19  7:14       ` Tom de Vries

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=20250915084105.23171-1-tdevries@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    /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