[PATCH] D121662: [WIP][WebAssembly] Add end-to-end codegen tests for wasm_simd128.h

Thomas Lively via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Tue Mar 15 11:26:03 PDT 2022


tlively added a comment.
Herald added a subscriber: asb.

Right now (after trying to upgrade my gdb) I get this error

  $ bin/llvm-lit ~/code/llvm-project/cross-project-tests/intrinsic-header-tests/wasm_simd128.c
  ...
  llvm-lit: /usr/local/google/home/tlively/code/llvm-project/llvm/utils/lit/lit/TestingConfig.py:103: fatal: unable to parse config file '/usr/local/google/home/tlively/code/llvm-project/cross-project-tests/lit.cfg.py', traceback: Traceback (most recent call last):
    File "/usr/local/google/home/tlively/code/llvm-project/llvm/utils/lit/lit/TestingConfig.py", line 92, in load_from_path
      exec(compile(data, path, 'exec'), cfg_globals, None)
    File "/usr/local/google/home/tlively/code/llvm-project/cross-project-tests/lit.cfg.py", line 249, in <module>
      if StrictVersion(gdb_version_string) < StrictVersion('10.1'):
    File "/usr/lib/python3.9/distutils/version.py", line 40, in __init__
      self.parse(vstring)
    File "/usr/lib/python3.9/distutils/version.py", line 137, in parse
      raise ValueError("invalid version number '%s'" % vstring)
  ValueError: invalid version number '10.1.90.20210103'

Before trying to upgrade my gdb, I had run this command:

  $ ninja check-intrinsic-headers
  [0/1] Running intrinsic header tests
  ...
  XFAIL some tests: use gdb version >= 10.1 to restore test coverage
  
  Testing Time: 0.04s
    Unsupported: 1

So aside from the problems with my invalid gdb version string, it looks like my test is still accidentally depending on having the correct gdb version.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D121662/new/

https://reviews.llvm.org/D121662



More information about the llvm-commits mailing list