Displaying 6 results from an estimated 6 matches for "host_triple".
Did you mean:
host_triplet
2019 Jun 14
3
Help required on running the regression tests
...a custom LLVM target implementation)
- Python 2.7.10 is already installed.
- From the command line (terminal app) I tried to execute python lit.site.cfg.py , however I get the following error:
File "/Users/joan/LLVM+CLANG/build/test/lit.site.cfg.py", line 6, in <module>
config.host_triple = "x86_64-apple-darwin16.7.0"
NameError: name 'config' is not defined
There seem to be something obvious that I miss, so any help is appreciated.
Please be aware that I’m an experienced C, C++, Obj-C programmer (now retired) but I do not speak a word of python.
Thanks,
John
--...
2010 Nov 23
2
[LLVMdev] LLVM unit and regression tests, enabled targets and conditions
...could produce unexpected successful result. Up
to me, we should deprecate XTARGET, if XFAIL accepts <condition>.
* We can extend declarative language to define variables. In this case
$each_target could be a test variable instead of a pre-defined
placeholder.
* target_triple is actually the host_triple. Shell we rename it?
Thanks
Galina
2017 Nov 25
2
PSA: debuginfo-tests workflow changing slightly
...t;
+config.llvm_plugin_ext = "@LLVM_PLUGIN_EXT@"
+config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@"
+config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@"
+config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@")
+config.host_triple = "@LLVM_HOST_TRIPLE@"
+config.target_triple = "@TARGET_TRIPLE@"
+config.host_arch = "@HOST_ARCH@"
+
+config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@"
+
+ at LIT_SITE_CFG_IN_FOOTER@
+
+# Let the main config do the real work.
+lit_config.load_config(config,...
2017 Dec 06
3
PSA: debuginfo-tests workflow changing slightly
...LLVM_PLUGIN_EXT@"
>> +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@"
>> +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@"
>> +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@")
>> +config.host_triple = "@LLVM_HOST_TRIPLE@"
>> +config.target_triple = "@TARGET_TRIPLE@"
>> +config.host_arch = "@HOST_ARCH@"
>> +
>> +config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@"
>> +
>> + at LIT_SITE_CFG_IN_FOOTER@
>> +
>> +...
2017 Dec 06
2
PSA: debuginfo-tests workflow changing slightly
...in_ext = "@LLVM_PLUGIN_EXT@"
> +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@"
> +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@"
> +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@")
> +config.host_triple = "@LLVM_HOST_TRIPLE@"
> +config.target_triple = "@TARGET_TRIPLE@"
> +config.host_arch = "@HOST_ARCH@"
> +
> +config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@"
> +
> + at LIT_SITE_CFG_IN_FOOTER@
> +
> +# Let the main config do the rea...
2017 Nov 22
2
PSA: debuginfo-tests workflow changing slightly
I sorta enjoy debugging stuff like this, so if you don't mind, I'll dig
into it once I get a chance -- traveling so, my access is a bit sketchy
right now.
I'll see if I can grab the logs and let you know if I find anything
interesting.
On Tue, Nov 21, 2017 at 7:04 PM, Zachary Turner <zturner at google.com> wrote:
> That change was added specifically to workaround a failure