2009-09-08 13:31:44 +08:00
|
|
|
# -*- Python -*-
|
|
|
|
|
|
|
|
|
|
# Configuration file for the 'lit' test runner.
|
|
|
|
|
|
|
|
|
|
import os
|
2010-11-29 08:20:09 +08:00
|
|
|
import sys
|
2011-01-04 01:30:25 +08:00
|
|
|
import re
|
2012-10-26 10:19:02 +08:00
|
|
|
import platform
|
2017-07-07 05:46:47 +08:00
|
|
|
import subprocess
|
2009-09-08 13:31:44 +08:00
|
|
|
|
2013-08-10 00:22:05 +08:00
|
|
|
import lit.util
|
|
|
|
|
import lit.formats
|
2017-09-17 02:46:21 +08:00
|
|
|
from lit.llvm import llvm_config
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
from lit.llvm.subst import FindTool
|
|
|
|
|
from lit.llvm.subst import ToolSubst
|
2013-08-10 00:22:05 +08:00
|
|
|
|
2009-09-08 13:31:44 +08:00
|
|
|
# name: The name of this test suite.
|
|
|
|
|
config.name = 'LLVM'
|
|
|
|
|
|
|
|
|
|
# testFormat: The test format to use to interpret tests.
|
2017-09-17 02:46:21 +08:00
|
|
|
config.test_format = lit.formats.ShTest(not llvm_config.use_lit_shell)
|
2009-09-08 13:31:44 +08:00
|
|
|
|
2013-08-09 04:59:13 +08:00
|
|
|
# suffixes: A list of file extensions to treat as test files. This is overriden
|
|
|
|
|
# by individual lit.local.cfg files in the test subdirectories.
|
2020-07-09 01:22:49 +08:00
|
|
|
config.suffixes = ['.ll', '.c', '.test', '.txt', '.s', '.mir', '.yaml']
|
2009-09-08 13:31:44 +08:00
|
|
|
|
2012-07-02 18:18:06 +08:00
|
|
|
# excludes: A list of directories to exclude from the testsuite. The 'Inputs'
|
|
|
|
|
# subdirectories contain auxiliary inputs for various tests in their parent
|
|
|
|
|
# directories.
|
2013-08-16 08:37:11 +08:00
|
|
|
config.excludes = ['Inputs', 'CMakeLists.txt', 'README.txt', 'LICENSE.txt']
|
2012-07-02 18:18:06 +08:00
|
|
|
|
2009-09-08 13:31:44 +08:00
|
|
|
# test_source_root: The root path where tests are located.
|
|
|
|
|
config.test_source_root = os.path.dirname(__file__)
|
|
|
|
|
|
|
|
|
|
# test_exec_root: The root path where tests should be run.
|
2017-09-16 06:10:46 +08:00
|
|
|
config.test_exec_root = os.path.join(config.llvm_obj_root, 'test')
|
2009-09-08 13:31:44 +08:00
|
|
|
|
2013-04-12 12:07:13 +08:00
|
|
|
# Tweak the PATH to include the tools dir.
|
2017-09-17 02:46:21 +08:00
|
|
|
llvm_config.with_environment('PATH', config.llvm_tools_dir, append_path=True)
|
2010-02-26 06:09:09 +08:00
|
|
|
|
2017-09-17 02:46:21 +08:00
|
|
|
# Propagate some variables from the host environment.
|
2017-10-07 01:54:27 +08:00
|
|
|
llvm_config.with_system_environment(
|
|
|
|
|
['HOME', 'INCLUDE', 'LIB', 'TMP', 'TEMP', 'ASAN_SYMBOLIZER_PATH', 'MSAN_SYMBOLIZER_PATH'])
|
2010-12-07 09:23:49 +08:00
|
|
|
|
2010-06-13 00:21:19 +08:00
|
|
|
|
2014-10-30 16:29:45 +08:00
|
|
|
# Set up OCAMLPATH to include newly built OCaml libraries.
|
2017-09-16 06:10:46 +08:00
|
|
|
top_ocaml_lib = os.path.join(config.llvm_lib_dir, 'ocaml')
|
|
|
|
|
llvm_ocaml_lib = os.path.join(top_ocaml_lib, 'llvm')
|
2017-09-17 02:46:21 +08:00
|
|
|
|
|
|
|
|
llvm_config.with_system_environment('OCAMLPATH')
|
|
|
|
|
llvm_config.with_environment('OCAMLPATH', top_ocaml_lib, append_path=True)
|
|
|
|
|
llvm_config.with_environment('OCAMLPATH', llvm_ocaml_lib, append_path=True)
|
|
|
|
|
|
|
|
|
|
llvm_config.with_system_environment('CAML_LD_LIBRARY_PATH')
|
2017-10-07 01:54:27 +08:00
|
|
|
llvm_config.with_environment(
|
|
|
|
|
'CAML_LD_LIBRARY_PATH', llvm_ocaml_lib, append_path=True)
|
2014-10-30 16:29:45 +08:00
|
|
|
|
2014-10-30 16:29:57 +08:00
|
|
|
# Set up OCAMLRUNPARAM to enable backtraces in OCaml tests.
|
2017-09-17 02:46:21 +08:00
|
|
|
llvm_config.with_environment('OCAMLRUNPARAM', 'b')
|
2014-10-30 16:29:57 +08:00
|
|
|
|
2016-08-05 06:01:38 +08:00
|
|
|
# Provide the path to asan runtime lib 'libclang_rt.asan_osx_dynamic.dylib' if
|
|
|
|
|
# available. This is darwin specific since it's currently only needed on darwin.
|
2017-10-07 01:54:27 +08:00
|
|
|
|
|
|
|
|
|
2016-08-05 06:01:38 +08:00
|
|
|
def get_asan_rtlib():
|
2017-10-07 01:54:27 +08:00
|
|
|
if not 'Address' in config.llvm_use_sanitizer or \
|
|
|
|
|
not 'Darwin' in config.host_os or \
|
|
|
|
|
not 'x86' in config.host_triple:
|
|
|
|
|
return ''
|
2016-08-05 06:01:38 +08:00
|
|
|
try:
|
|
|
|
|
import glob
|
|
|
|
|
except:
|
2017-10-07 01:54:27 +08:00
|
|
|
print('glob module not found, skipping get_asan_rtlib() lookup')
|
|
|
|
|
return ''
|
2016-08-05 06:01:38 +08:00
|
|
|
# The libclang_rt.asan_osx_dynamic.dylib path is obtained using the relative
|
|
|
|
|
# path from the host cc.
|
2017-10-07 01:54:27 +08:00
|
|
|
host_lib_dir = os.path.join(os.path.dirname(config.host_cc), '../lib')
|
2016-08-05 06:01:38 +08:00
|
|
|
asan_dylib_dir_pattern = host_lib_dir + \
|
2017-10-07 01:54:27 +08:00
|
|
|
'/clang/*/lib/darwin/libclang_rt.asan_osx_dynamic.dylib'
|
2016-08-05 06:01:38 +08:00
|
|
|
found_dylibs = glob.glob(asan_dylib_dir_pattern)
|
|
|
|
|
if len(found_dylibs) != 1:
|
2017-10-07 01:54:27 +08:00
|
|
|
return ''
|
2016-08-05 06:01:38 +08:00
|
|
|
return found_dylibs[0]
|
|
|
|
|
|
2021-01-21 10:37:22 +08:00
|
|
|
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
llvm_config.use_default_substitutions()
|
|
|
|
|
|
|
|
|
|
# Add site-specific substitutions.
|
|
|
|
|
config.substitutions.append(('%llvmshlibdir', config.llvm_shlib_dir))
|
|
|
|
|
config.substitutions.append(('%shlibext', config.llvm_shlib_ext))
|
2021-04-28 07:36:45 +08:00
|
|
|
config.substitutions.append(('%pluginext', config.llvm_plugin_ext))
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
config.substitutions.append(('%exeext', config.llvm_exe_ext))
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
lli_args = []
|
Introduce llvm::sys::getProcessTriple() function.
In r143502, we renamed getHostTriple() to getDefaultTargetTriple()
as part of work to allow the user to supply a different default
target triple at configure time. This change also affected the JIT.
However, it is inappropriate to use the default target triple in the
JIT in most circumstances because this will not necessarily match
the current architecture used by the process, leading to illegal
instruction and other such errors at run time.
Introduce the getProcessTriple() function for use in the JIT and
its clients, and cause the JIT to use it. On architectures with a
single bitness, the host and process triples are identical. On other
architectures, the host triple represents the architecture of the
host CPU, while the process triple represents the architecture used
by the host CPU to interpret machine code within the current process.
For example, when executing 32-bit code on a 64-bit Linux machine,
the host triple may be 'x86_64-unknown-linux-gnu', while the process
triple may be 'i386-unknown-linux-gnu'.
This fixes JIT for the 32-on-64-bit (and vice versa) build on non-Apple
platforms.
Differential Revision: http://llvm-reviews.chandlerc.com/D254
llvm-svn: 172627
2013-01-17 01:27:22 +08:00
|
|
|
# The target triple used by default by lli is the process target triple (some
|
|
|
|
|
# triple appropriate for generating code for the current process) but because
|
|
|
|
|
# we don't support COFF in MCJIT well enough for the tests, force ELF format on
|
|
|
|
|
# Windows. FIXME: the process target triple should be used here, but this is
|
|
|
|
|
# difficult to obtain on Windows.
|
2018-08-09 10:16:18 +08:00
|
|
|
if re.search(r'cygwin|windows-gnu|windows-msvc', config.host_triple):
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
lli_args = ['-mtriple=' + config.host_triple + '-elf']
|
|
|
|
|
|
|
|
|
|
llc_args = []
|
2012-10-03 02:38:34 +08:00
|
|
|
|
2018-08-09 10:16:18 +08:00
|
|
|
# Similarly, have a macro to use llc with DWARF even when the host is Windows
|
|
|
|
|
if re.search(r'windows-msvc', config.target_triple):
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
llc_args = [' -mtriple=' +
|
2018-08-09 10:16:18 +08:00
|
|
|
config.target_triple.replace('-msvc', '-gnu')]
|
2009-09-08 13:31:44 +08:00
|
|
|
|
2016-08-05 06:01:38 +08:00
|
|
|
# Provide the path to asan runtime lib if available. On darwin, this lib needs
|
|
|
|
|
# to be loaded via DYLD_INSERT_LIBRARIES before libLTO.dylib in case the files
|
|
|
|
|
# to be linked contain instrumented sanitizer code.
|
2016-08-05 07:58:30 +08:00
|
|
|
ld64_cmd = config.ld64_executable
|
|
|
|
|
asan_rtlib = get_asan_rtlib()
|
|
|
|
|
if asan_rtlib:
|
2017-10-07 01:54:27 +08:00
|
|
|
ld64_cmd = 'DYLD_INSERT_LIBRARIES={} {}'.format(asan_rtlib, ld64_cmd)
|
2021-06-23 00:21:12 +08:00
|
|
|
if config.osx_sysroot:
|
|
|
|
|
ld64_cmd = '{} -syslibroot {}'.format(ld64_cmd, config.osx_sysroot)
|
2016-08-05 06:01:38 +08:00
|
|
|
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
ocamlc_command = '%s ocamlc -cclib -L%s %s' % (
|
|
|
|
|
config.ocamlfind_executable, config.llvm_lib_dir, config.ocaml_flags)
|
|
|
|
|
ocamlopt_command = 'true'
|
2017-01-07 05:33:48 +08:00
|
|
|
if config.have_ocamlopt:
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
ocamlopt_command = '%s ocamlopt -cclib -L%s -cclib -Wl,-rpath,%s %s' % (
|
|
|
|
|
config.ocamlfind_executable, config.llvm_lib_dir, config.llvm_lib_dir, config.ocaml_flags)
|
|
|
|
|
|
2017-11-30 01:07:41 +08:00
|
|
|
opt_viewer_cmd = '%s %s/tools/opt-viewer/opt-viewer.py' % (sys.executable, config.llvm_src_root)
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
|
2021-02-22 22:01:54 +08:00
|
|
|
llvm_original_di_preservation_cmd = os.path.join(
|
|
|
|
|
config.llvm_src_root,'utils', 'llvm-original-di-preservation.py')
|
|
|
|
|
config.substitutions.append(
|
|
|
|
|
('%llvm-original-di-preservation', "'%s' %s" % (
|
|
|
|
|
config.python_executable, llvm_original_di_preservation_cmd)))
|
|
|
|
|
|
2019-10-02 15:00:01 +08:00
|
|
|
llvm_locstats_tool = os.path.join(config.llvm_tools_dir, 'llvm-locstats')
|
|
|
|
|
config.substitutions.append(
|
|
|
|
|
('%llvm-locstats', "'%s' %s" % (config.python_executable, llvm_locstats_tool)))
|
|
|
|
|
config.llvm_locstats_used = os.path.exists(llvm_locstats_tool)
|
|
|
|
|
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
tools = [
|
|
|
|
|
ToolSubst('%lli', FindTool('lli'), post='.', extra_args=lli_args),
|
|
|
|
|
ToolSubst('%llc_dwarf', FindTool('llc'), extra_args=llc_args),
|
|
|
|
|
ToolSubst('%go', config.go_executable, unresolved='ignore'),
|
|
|
|
|
ToolSubst('%gold', config.gold_executable, unresolved='ignore'),
|
|
|
|
|
ToolSubst('%ld64', ld64_cmd, unresolved='ignore'),
|
|
|
|
|
ToolSubst('%ocamlc', ocamlc_command, unresolved='ignore'),
|
|
|
|
|
ToolSubst('%ocamlopt', ocamlopt_command, unresolved='ignore'),
|
2017-11-30 01:07:41 +08:00
|
|
|
ToolSubst('%opt-viewer', opt_viewer_cmd),
|
2018-04-13 13:03:28 +08:00
|
|
|
ToolSubst('%llvm-objcopy', FindTool('llvm-objcopy')),
|
2018-05-08 05:07:01 +08:00
|
|
|
ToolSubst('%llvm-strip', FindTool('llvm-strip')),
|
2019-11-20 15:30:52 +08:00
|
|
|
ToolSubst('%llvm-install-name-tool', FindTool('llvm-install-name-tool')),
|
2020-09-19 09:11:22 +08:00
|
|
|
ToolSubst('%llvm-bitcode-strip', FindTool('llvm-bitcode-strip')),
|
2020-08-04 01:17:55 +08:00
|
|
|
ToolSubst('%split-file', FindTool('split-file')),
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
]
|
|
|
|
|
|
|
|
|
|
# FIXME: Why do we have both `lli` and `%lli` that do slightly different things?
|
|
|
|
|
tools.extend([
|
2018-09-25 21:59:35 +08:00
|
|
|
'dsymutil', 'lli', 'lli-child-target', 'llvm-ar', 'llvm-as',
|
2021-02-09 05:37:03 +08:00
|
|
|
'llvm-addr2line', 'llvm-bcanalyzer', 'llvm-bitcode-strip', 'llvm-config',
|
2021-12-15 01:29:17 +08:00
|
|
|
'llvm-cov', 'llvm-cxxdump', 'llvm-cvtres', 'llvm-debuginfod-find',
|
|
|
|
|
'llvm-diff', 'llvm-dis', 'llvm-dwarfdump', 'llvm-dlltool', 'llvm-exegesis',
|
|
|
|
|
'llvm-extract', 'llvm-isel-fuzzer', 'llvm-ifs',
|
2020-01-24 08:25:30 +08:00
|
|
|
'llvm-install-name-tool', 'llvm-jitlink', 'llvm-opt-fuzzer', 'llvm-lib',
|
2019-04-21 04:05:30 +08:00
|
|
|
'llvm-link', 'llvm-lto', 'llvm-lto2', 'llvm-mc', 'llvm-mca',
|
2021-04-15 22:55:22 +08:00
|
|
|
'llvm-modextract', 'llvm-nm', 'llvm-objcopy', 'llvm-objdump', 'llvm-otool',
|
2021-04-22 09:02:11 +08:00
|
|
|
'llvm-pdbutil', 'llvm-profdata', 'llvm-profgen', 'llvm-ranlib', 'llvm-rc', 'llvm-readelf',
|
2021-10-29 09:51:52 +08:00
|
|
|
'llvm-readobj', 'llvm-remark-size-diff', 'llvm-rtdyld', 'llvm-sim',
|
|
|
|
|
'llvm-size', 'llvm-split', 'llvm-stress', 'llvm-strings', 'llvm-strip',
|
|
|
|
|
'llvm-tblgen', 'llvm-tapi-diff', 'llvm-undname', 'llvm-windres',
|
|
|
|
|
'llvm-c-test', 'llvm-cxxfilt', 'llvm-xray', 'yaml2obj', 'obj2yaml',
|
|
|
|
|
'yaml-bench', 'verify-uselistorder', 'bugpoint', 'llc', 'llvm-symbolizer',
|
|
|
|
|
'opt', 'sancov', 'sanstats'])
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
|
|
|
|
|
# The following tools are optional
|
|
|
|
|
tools.extend([
|
2020-02-25 01:11:15 +08:00
|
|
|
ToolSubst('llvm-go', unresolved='ignore'),
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
ToolSubst('llvm-mt', unresolved='ignore'),
|
|
|
|
|
ToolSubst('Kaleidoscope-Ch3', unresolved='ignore'),
|
|
|
|
|
ToolSubst('Kaleidoscope-Ch4', unresolved='ignore'),
|
|
|
|
|
ToolSubst('Kaleidoscope-Ch5', unresolved='ignore'),
|
|
|
|
|
ToolSubst('Kaleidoscope-Ch6', unresolved='ignore'),
|
|
|
|
|
ToolSubst('Kaleidoscope-Ch7', unresolved='ignore'),
|
2020-08-27 02:44:57 +08:00
|
|
|
ToolSubst('Kaleidoscope-Ch8', unresolved='ignore'),
|
2021-04-07 15:44:18 +08:00
|
|
|
ToolSubst('LLJITWithThinLTOSummaries', unresolved='ignore'),
|
2021-07-01 03:44:54 +08:00
|
|
|
ToolSubst('LLJITWithRemoteDebugging', unresolved='ignore'),
|
|
|
|
|
ToolSubst('OrcV2CBindingsBasicUsage', unresolved='ignore'),
|
|
|
|
|
ToolSubst('OrcV2CBindingsAddObjectFile', unresolved='ignore'),
|
|
|
|
|
ToolSubst('OrcV2CBindingsRemovableCode', unresolved='ignore'),
|
2021-07-01 03:47:43 +08:00
|
|
|
ToolSubst('OrcV2CBindingsReflectProcessSymbols', unresolved='ignore'),
|
2021-07-18 22:22:34 +08:00
|
|
|
ToolSubst('OrcV2CBindingsLazy', unresolved='ignore'),
|
2022-04-15 02:37:44 +08:00
|
|
|
ToolSubst('OrcV2CBindingsVeryLazy', unresolved='ignore'),
|
|
|
|
|
ToolSubst('dxil-dis', unresolved='ignore')])
|
[lit] Improve tool substitution in lit.
This addresses two sources of inconsistency in test configuration
files.
1. Substitution boundaries. Previously you would specify a
substitution, such as 'lli', and then additionally a set
of characters that should fail to match before and after
the tool. This was used, for example, so that matches that
are parts of full paths would not be replaced. But not all
tools did this, and those that did would often re-invent
the set of characters themselves, leading to inconsistency.
Now, every tool substitution defaults to using a sane set
of reasonable defaults and you have to explicitly opt out
of it. This actually fixed a few latent bugs that were
never being surfaced, but only on accident.
2. There was no standard way for the system to decide how to
locate a tool. Sometimes you have an explicit path, sometimes
we would search for it and build up a path ourselves, and
sometimes we would build up a full command line. Furthermore,
there was no standardized way to handle missing tools. Do we
warn, fail, ignore, etc? All of this is now encapsulated in
the ToolSubst class. You either specify an exact command to
run, or an instance of FindTool('<tool-name>') and everything
else just works. Furthermore, you can specify an action to
take if the tool cannot be resolved.
Differential Revision: https://reviews.llvm.org/D38565
llvm-svn: 315085
2017-10-07 01:54:46 +08:00
|
|
|
|
|
|
|
|
llvm_config.add_tool_substitutions(tools, config.llvm_tools_dir)
|
2015-09-03 02:03:01 +08:00
|
|
|
|
2017-10-07 01:54:27 +08:00
|
|
|
# Targets
|
2014-06-10 06:42:55 +08:00
|
|
|
|
|
|
|
|
config.targets = frozenset(config.targets_to_build.split())
|
|
|
|
|
|
2016-08-11 03:03:18 +08:00
|
|
|
for arch in config.targets_to_build.split():
|
|
|
|
|
config.available_features.add(arch.lower() + '-registered-target')
|
|
|
|
|
|
2017-10-07 01:54:27 +08:00
|
|
|
# Features
|
2017-11-03 07:14:55 +08:00
|
|
|
known_arches = ["x86_64", "mips64", "ppc64", "aarch64"]
|
2017-11-04 14:55:55 +08:00
|
|
|
if (config.host_ldflags.find("-m32") < 0
|
|
|
|
|
and any(config.llvm_host_triple.startswith(x) for x in known_arches)):
|
2017-11-03 07:14:55 +08:00
|
|
|
config.available_features.add("llvm-64-bits")
|
2010-11-29 08:20:09 +08:00
|
|
|
|
2019-05-01 23:36:18 +08:00
|
|
|
config.available_features.add("host-byteorder-" + sys.byteorder + "-endian")
|
|
|
|
|
|
2019-05-14 22:51:54 +08:00
|
|
|
if sys.platform in ['win32']:
|
|
|
|
|
# ExecutionEngine, no weak symbols in COFF.
|
|
|
|
|
config.available_features.add('uses_COFF')
|
|
|
|
|
else:
|
|
|
|
|
# Others/can-execute.txt
|
2013-06-26 18:56:44 +08:00
|
|
|
config.available_features.add('can-execute')
|
|
|
|
|
|
2010-11-29 08:20:09 +08:00
|
|
|
# Loadable module
|
2019-05-17 14:41:04 +08:00
|
|
|
if config.has_plugins:
|
|
|
|
|
config.available_features.add('plugins')
|
2011-06-23 07:23:19 +08:00
|
|
|
|
2019-06-08 23:37:47 +08:00
|
|
|
if config.build_examples:
|
|
|
|
|
config.available_features.add('examples')
|
|
|
|
|
|
2020-01-10 17:05:30 +08:00
|
|
|
if config.linked_bye_extension:
|
2019-06-08 23:37:47 +08:00
|
|
|
config.substitutions.append(('%llvmcheckext', 'CHECK-EXT'))
|
|
|
|
|
config.substitutions.append(('%loadbye', ''))
|
2020-03-27 01:09:13 +08:00
|
|
|
config.substitutions.append(('%loadnewpmbye', ''))
|
2019-06-08 23:37:47 +08:00
|
|
|
else:
|
|
|
|
|
config.substitutions.append(('%llvmcheckext', 'CHECK-NOEXT'))
|
|
|
|
|
config.substitutions.append(('%loadbye',
|
2020-01-10 17:05:30 +08:00
|
|
|
'-load={}/Bye{}'.format(config.llvm_shlib_dir,
|
2020-03-27 01:09:13 +08:00
|
|
|
config.llvm_shlib_ext)))
|
|
|
|
|
config.substitutions.append(('%loadnewpmbye',
|
|
|
|
|
'-load-pass-plugin={}/Bye{}'
|
|
|
|
|
.format(config.llvm_shlib_dir,
|
|
|
|
|
config.llvm_shlib_ext)))
|
|
|
|
|
|
2019-06-08 23:37:47 +08:00
|
|
|
|
2017-01-07 05:33:54 +08:00
|
|
|
# Static libraries are not built if BUILD_SHARED_LIBS is ON.
|
2017-10-19 03:37:30 +08:00
|
|
|
if not config.build_shared_libs and not config.link_llvm_dylib:
|
2017-10-07 01:54:27 +08:00
|
|
|
config.available_features.add('static-libs')
|
2017-01-07 05:33:54 +08:00
|
|
|
|
2021-09-04 02:52:53 +08:00
|
|
|
if config.link_llvm_dylib:
|
|
|
|
|
config.available_features.add('llvm-dylib')
|
|
|
|
|
config.substitutions.append(
|
|
|
|
|
('%llvmdylib',
|
|
|
|
|
'{}/libLLVM-{}{}'.format(config.llvm_shlib_dir,
|
|
|
|
|
config.llvm_dylib_version,
|
|
|
|
|
config.llvm_shlib_ext)))
|
|
|
|
|
|
2020-06-10 05:50:50 +08:00
|
|
|
if config.have_tf_aot:
|
|
|
|
|
config.available_features.add("have_tf_aot")
|
|
|
|
|
|
2020-07-16 07:02:15 +08:00
|
|
|
if config.have_tf_api:
|
|
|
|
|
config.available_features.add("have_tf_api")
|
|
|
|
|
|
2021-10-14 01:36:08 +08:00
|
|
|
if config.llvm_inliner_model_autogenerated:
|
|
|
|
|
config.available_features.add("llvm_inliner_model_autogenerated")
|
|
|
|
|
|
2022-01-20 09:51:42 +08:00
|
|
|
if config.llvm_raevict_model_autogenerated:
|
|
|
|
|
config.available_features.add("llvm_raevict_model_autogenerated")
|
|
|
|
|
|
2018-01-08 10:48:41 +08:00
|
|
|
def have_cxx_shared_library():
|
|
|
|
|
readobj_exe = lit.util.which('llvm-readobj', config.llvm_tools_dir)
|
|
|
|
|
if not readobj_exe:
|
|
|
|
|
print('llvm-readobj not found')
|
|
|
|
|
return False
|
|
|
|
|
|
|
|
|
|
try:
|
|
|
|
|
readobj_cmd = subprocess.Popen(
|
2021-07-16 01:26:21 +08:00
|
|
|
[readobj_exe, '--needed-libs', readobj_exe], stdout=subprocess.PIPE)
|
2018-01-08 10:48:41 +08:00
|
|
|
except OSError:
|
|
|
|
|
print('could not exec llvm-readobj')
|
|
|
|
|
return False
|
|
|
|
|
|
|
|
|
|
readobj_out = readobj_cmd.stdout.read().decode('ascii')
|
|
|
|
|
readobj_cmd.wait()
|
|
|
|
|
|
|
|
|
|
regex = re.compile(r'(libc\+\+|libstdc\+\+|msvcp).*\.(so|dylib|dll)')
|
|
|
|
|
needed_libs = False
|
|
|
|
|
for line in readobj_out.splitlines():
|
|
|
|
|
if 'NeededLibraries [' in line:
|
|
|
|
|
needed_libs = True
|
|
|
|
|
if ']' in line:
|
|
|
|
|
needed_libs = False
|
|
|
|
|
if needed_libs and regex.search(line.lower()):
|
|
|
|
|
return True
|
|
|
|
|
return False
|
|
|
|
|
|
|
|
|
|
if have_cxx_shared_library():
|
|
|
|
|
config.available_features.add('cxx-shared-library')
|
|
|
|
|
|
[lit][tests]Add feature libcxx-used and use it in llvm-*-fuzzer tests
When a LLVM binary such as llvm-*-fuzzer is built with libc++, it has dependency on libc++. The path to find shared libraries specified in llvm-*-fuzzer is relative. As a result, these binaries cannot be copied to an arbitrary directory and launched from there. Changes in this patch add a LIT feature to indicate that libc++ is used to build and, based on the feature exclude test cases that test by copying llvm-*-fuzzer binaries to a directory.
Reviewers: hubert.reinterpretcast, dberris, amyk, jasonliu, EricWF
Reviewed By: hubert.reinterpretcast, amyk
Subscribers: javed.absar, jsji, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D61265
llvm-svn: 360672
2019-05-14 21:54:33 +08:00
|
|
|
if config.libcxx_used:
|
|
|
|
|
config.available_features.add('libcxx-used')
|
|
|
|
|
|
2015-09-16 13:34:32 +08:00
|
|
|
# LLVM can be configured with an empty default triple
|
|
|
|
|
# Some tests are "generic" and require a valid default triple
|
|
|
|
|
if config.target_triple:
|
2017-10-07 01:54:27 +08:00
|
|
|
config.available_features.add('default_triple')
|
2022-03-22 18:14:25 +08:00
|
|
|
# Direct object generation
|
2022-03-22 18:14:56 +08:00
|
|
|
if not config.target_triple.startswith(("nvptx", "xcore")):
|
2022-03-22 18:14:25 +08:00
|
|
|
config.available_features.add('object-emission')
|
2013-09-13 18:59:01 +08:00
|
|
|
|
2011-11-28 13:09:15 +08:00
|
|
|
import subprocess
|
2014-07-28 07:11:06 +08:00
|
|
|
|
2017-10-07 01:54:27 +08:00
|
|
|
|
2014-07-28 07:11:06 +08:00
|
|
|
def have_ld_plugin_support():
|
2018-06-20 23:32:47 +08:00
|
|
|
if not os.path.exists(os.path.join(config.llvm_shlib_dir, 'LLVMgold' + config.llvm_shlib_ext)):
|
2014-07-28 07:11:06 +08:00
|
|
|
return False
|
|
|
|
|
|
2017-10-07 01:54:27 +08:00
|
|
|
ld_cmd = subprocess.Popen(
|
|
|
|
|
[config.gold_executable, '--help'], stdout=subprocess.PIPE, env={'LANG': 'C'})
|
2015-01-05 22:18:04 +08:00
|
|
|
ld_out = ld_cmd.stdout.read().decode()
|
2014-07-28 07:11:06 +08:00
|
|
|
ld_cmd.wait()
|
|
|
|
|
|
2014-11-11 13:27:12 +08:00
|
|
|
if not '-plugin' in ld_out:
|
|
|
|
|
return False
|
|
|
|
|
|
|
|
|
|
# check that the used emulations are supported.
|
|
|
|
|
emu_line = [l for l in ld_out.split('\n') if 'supported emulations' in l]
|
|
|
|
|
if len(emu_line) != 1:
|
|
|
|
|
return False
|
|
|
|
|
emu_line = emu_line[0]
|
|
|
|
|
fields = emu_line.split(':')
|
|
|
|
|
if len(fields) != 3:
|
|
|
|
|
return False
|
|
|
|
|
emulations = fields[2].split()
|
2015-03-20 02:23:31 +08:00
|
|
|
if 'elf_x86_64' not in emulations:
|
2014-11-11 13:27:12 +08:00
|
|
|
return False
|
2015-03-20 02:23:31 +08:00
|
|
|
if 'elf32ppc' in emulations:
|
|
|
|
|
config.available_features.add('ld_emu_elf32ppc')
|
2014-11-11 13:27:12 +08:00
|
|
|
|
2017-10-07 01:54:27 +08:00
|
|
|
ld_version = subprocess.Popen(
|
|
|
|
|
[config.gold_executable, '--version'], stdout=subprocess.PIPE, env={'LANG': 'C'})
|
2015-02-14 17:05:56 +08:00
|
|
|
if not 'GNU gold' in ld_version.stdout.read().decode():
|
2014-07-28 07:11:06 +08:00
|
|
|
return False
|
|
|
|
|
ld_version.wait()
|
|
|
|
|
|
|
|
|
|
return True
|
|
|
|
|
|
2017-10-07 01:54:27 +08:00
|
|
|
|
2014-07-28 07:11:06 +08:00
|
|
|
if have_ld_plugin_support():
|
|
|
|
|
config.available_features.add('ld_plugin')
|
|
|
|
|
|
2017-10-07 01:54:27 +08:00
|
|
|
|
2015-03-20 07:55:38 +08:00
|
|
|
def have_ld64_plugin_support():
|
2019-01-18 11:36:04 +08:00
|
|
|
if not os.path.exists(os.path.join(config.llvm_shlib_dir, 'libLTO' + config.llvm_shlib_ext)):
|
|
|
|
|
return False
|
|
|
|
|
|
|
|
|
|
if config.ld64_executable == '':
|
2015-03-20 07:55:38 +08:00
|
|
|
return False
|
|
|
|
|
|
2017-10-07 01:54:27 +08:00
|
|
|
ld_cmd = subprocess.Popen(
|
|
|
|
|
[config.ld64_executable, '-v'], stderr=subprocess.PIPE)
|
2015-03-20 07:55:38 +08:00
|
|
|
ld_out = ld_cmd.stderr.read().decode()
|
|
|
|
|
ld_cmd.wait()
|
|
|
|
|
|
|
|
|
|
if 'ld64' not in ld_out or 'LTO' not in ld_out:
|
|
|
|
|
return False
|
|
|
|
|
|
|
|
|
|
return True
|
|
|
|
|
|
2017-10-07 01:54:27 +08:00
|
|
|
|
2015-03-20 07:55:38 +08:00
|
|
|
if have_ld64_plugin_support():
|
|
|
|
|
config.available_features.add('ld64_plugin')
|
|
|
|
|
|
2020-08-27 22:50:25 +08:00
|
|
|
# Ask llvm-config about asserts
|
2017-09-19 06:26:48 +08:00
|
|
|
llvm_config.feature_config(
|
2020-09-17 05:51:41 +08:00
|
|
|
[('--assertion-mode', {'ON': 'asserts'}),
|
|
|
|
|
('--build-mode', {'[Dd][Ee][Bb][Uu][Gg]': 'debug'})])
|
2013-07-12 07:36:57 +08:00
|
|
|
|
2013-08-21 13:02:12 +08:00
|
|
|
if 'darwin' == sys.platform:
|
2020-01-13 21:35:57 +08:00
|
|
|
cmd = ['sysctl', 'hw.optional.fma']
|
|
|
|
|
sysctl_cmd = subprocess.Popen(cmd, stdout=subprocess.PIPE)
|
|
|
|
|
|
|
|
|
|
# Non zero return, probably a permission issue
|
|
|
|
|
if sysctl_cmd.wait():
|
|
|
|
|
print(
|
|
|
|
|
"Warning: sysctl exists but calling \"{}\" failed, defaulting to no fma3.".format(
|
|
|
|
|
" ".join(cmd)))
|
|
|
|
|
else:
|
|
|
|
|
result = sysctl_cmd.stdout.read().decode('ascii')
|
|
|
|
|
if 'hw.optional.fma: 1' in result:
|
|
|
|
|
config.available_features.add('fma3')
|
2013-08-21 13:02:12 +08:00
|
|
|
|
2021-10-31 21:32:56 +08:00
|
|
|
# .debug_frame is not emitted for targeting Windows x64, arm64, or AIX.
|
|
|
|
|
if not re.match(r'^(x86_64|arm64|powerpc|powerpc64).*-(windows-gnu|windows-msvc|aix)', config.target_triple):
|
2014-06-22 20:35:39 +08:00
|
|
|
config.available_features.add('debug_frame')
|
|
|
|
|
|
2016-05-24 05:34:12 +08:00
|
|
|
if config.have_libxar:
|
|
|
|
|
config.available_features.add('xar')
|
2017-06-07 08:22:52 +08:00
|
|
|
|
2018-09-27 00:26:59 +08:00
|
|
|
if config.enable_threads:
|
|
|
|
|
config.available_features.add('thread_support')
|
|
|
|
|
|
2020-07-25 06:47:38 +08:00
|
|
|
if config.have_libxml2:
|
2017-07-27 09:11:53 +08:00
|
|
|
config.available_features.add('libxml2')
|
2017-11-30 01:07:41 +08:00
|
|
|
|
2021-12-15 01:29:17 +08:00
|
|
|
if config.have_curl:
|
|
|
|
|
config.available_features.add('curl')
|
|
|
|
|
|
2017-11-30 01:07:41 +08:00
|
|
|
if config.have_opt_viewer_modules:
|
|
|
|
|
config.available_features.add('have_opt_viewer_modules')
|
2020-09-17 05:51:41 +08:00
|
|
|
|
|
|
|
|
if config.expensive_checks:
|
|
|
|
|
config.available_features.add('expensive_checks')
|
2021-11-05 09:07:15 +08:00
|
|
|
|
|
|
|
|
if "MemoryWithOrigins" in config.llvm_use_sanitizer:
|
|
|
|
|
config.available_features.add('use_msan_with_origins')
|
2022-01-10 01:20:38 +08:00
|
|
|
|
|
|
|
|
def exclude_unsupported_files_for_aix(dirname):
|
|
|
|
|
for filename in os.listdir(dirname):
|
|
|
|
|
source_path = os.path.join( dirname, filename)
|
|
|
|
|
if os.path.isdir(source_path):
|
|
|
|
|
continue
|
|
|
|
|
f = open(source_path, 'r')
|
|
|
|
|
try:
|
|
|
|
|
data = f.read()
|
|
|
|
|
# 64-bit object files are not supported on AIX, so exclude the tests.
|
|
|
|
|
if ('-emit-obj' in data or '-filetype=obj' in data) and '64' in config.target_triple:
|
|
|
|
|
config.excludes += [ filename ]
|
|
|
|
|
finally:
|
|
|
|
|
f.close()
|
|
|
|
|
|
|
|
|
|
if 'aix' in config.target_triple:
|
|
|
|
|
for directory in ('/CodeGen/X86', '/DebugInfo', '/DebugInfo/X86', '/DebugInfo/Generic', '/LTO/X86', '/Linker'):
|
|
|
|
|
exclude_unsupported_files_for_aix(config.test_source_root + directory)
|
|
|
|
|
|