filecheck-ng 0.1.2

A Python-native clone of LLVMs FileCheck tool

filecheck - A Python-native clone of LLVMs FileCheck tool

This tries to be as close a clone of LLVMs FileCheck as possible, without going crazy. It currently passes 1530 out of 1645 (93%) of LLVMs MLIR filecheck tests.

There are some features that are left out for now (e.g.a pseudo-numeric variables and parts of numeric substitution ).

The codebase is fully type checked by pyright, and automatically formatted using black. We aim to have tests covering everything from normal matching down to error messages.

Features:

Here's an overview of all FileCheck features and their implementation status.

• Checks:
  • CHECK
  • CHECK-NEXT
  • CHECK-NOT (Bug: #10)
  • CHECK-LABEL (Bug: #8)
  • CHECK-EMPTY
  • CHECK-SAME
  • CHECK-DAG
  • CHECK-COUNT
• Flags:
  • --check-prefix
  • --check-prefixes (Tracking: #13)
  • --comment-prefixes
  • --allow-unused-prefixes
  • --input-file
  • --match-full-lines
  • --strict-whitespace (Bug: #6)
  • --ignore-case
  • --implicit-check-not
  • --dump-input
  • --dump-input-context
  • --dump-input-filter
  • --enable-var-scope
  • -D<VAR=VALUE>
  • -D#<FMT>,<NUMVAR>=<NUMERIC EXPRESSION>
  • -version
  • -v
  • -vv
  • --allow-deprecated-dag-overlap Not sure what this means yet.
  • --allow-empty
  • --color No color support yet
• Base Features:
  • Regex patterns (Bugs: #3, #7, #9)
  • Captures and Capture Matches (Diverges: #5, #12 Bug: #11)
  • Numeric Captures
  • Numeric Substitutions (jesus christ, wtf man)
  • Literal matching (CHECK{LITERAL})
  • Weird regex features ([:xdigits:] and friends) (Bug: #4)
  • Correct(?) handling of matching check lines
• Testing:
  • Base cases
  • Negative tests
  • Error messages (started)
  • Lots of edge cases
  • MLIR/xDSL integration tests
• UX:
  • Good error messages: I have some error messages, but could be a lot better
    • Parse errors
    • Matching errors
    • Malformed regexes
• Infrastructure:
  • Formatting: black
  • Pyright
  • pre-commit
  • CI for everything

We are open to PRs for bugfixes or any features listed here.

Differences to LLVMs FileCheck:

We want to be as close as possible to the original FileCheck, and document our differences very clearly.

If you encounter a difference that is not documented here, feel free to file a bug report.

Better Regexes

We use pythons regex library, which is a flavour of a Perl compatible regular expression (PCRE), instead of FileChecks POSIX regex falvour.

Example:

// LLVM filecheck:
// CHECK: %{{[:alnum:]+}}, %{{[:digit:]+}}

// our fileheck:
// CHECK: %{{[a-zA-Z0-9]+}}, %{{\d+}}

Some effort is made to translate character classes from POSIX to PCRE, although it might be wrong in edge cases.

Relaxed Matchings:

We relax some of the matching rules, like:

• Allow a file to start with CHECK-NEXT

No Numerical Substitution

While our filecheck supports numeric capture ([[#%.3x,VAR:]] will capture a three-digit hex number), we don't support arithmetic expressions on these captured values at the moment. We also don't support the "Pseudo Numeric Variable" @LINE.

Special Feature Flags:

This version of filecheck implements some non-standard extensions to LLVMs filecheck. These are disabled by default but can be enabled through the environment variable FILECHECK_FEATURE_ENABLE=.... Avialable extensions are documented here:

• MLIR_REGEX_CLS: Add additional special regex matchers to match MLIR/LLVM constructs:
  • \V will match any SSA value name