-- Failed to find LLVM FileCheck -- git version: v0.0.0-dirty normalized to 0.0.0 -- Version: 1.6.0 -- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES -- failed to compile -- Performing Test HAVE_GNU_POSIX_REGEX -
-- Failed to find LLVM FileCheck -- git version: v0.0.0-dirty normalized to 0.0.0 -- Version: 1.6.0 -- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES -- failed to compile -- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile -- Performing Test HAVE_POSIX_REGEX -- success -- ...
Apologies for the large change, I looked for ways to break this up and all of the ones I saw added real complexity. This change focuses on the option's prefixed names and the array of prefixes. These are present in every option and the dominant source of dynamic relocations for PIE or ...
failed with exit code 139 (use -v to see invocation) clang version 17.0.5 Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /usr/bin clang: note: diagnostic msg: *** PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(...
wasm-objdump-xwasm_test.o[zhongxiao.yzx@saas-imagestest]$wasm-objdump-xwasm_test.owasm_test.o:fileformatwasm0x1SectionDetails:Type[2]:-type[0](i32,i32)->i32-type[1]()->i32Import[3]:-memory[0]pages:initial=0<-env.__linear_memory-table[0]type=funcrefinitial=0<-env.__indirect_func...
[llvm-objdump][ELF]Fix crash when reading strings from .dynstr (#125679) This change introduces a check for the strtab offset to prevent llvm-objdump from crashing when processing malformed ELF files. It provide a minimal reproduce test for ...
0395868("[BPF] Make llvm-objdump disasm default cpu v4 (#102166)"). Add two macros, __BPF_FEATURE_LOAD_ACQUIRE and __BPF_FEATURE_STORE_RELEASE, to let developers detect these new features in source code. They can also be disabled using two new llc options, ...
return createStringError("Failed to open file " + *Filename); // TODO: Current use case involves LLVM IR bitcode files as input.-// This will be extended to support objects and SPIR-V IR files.+// This will be extended to support SPIR-V IR files.if (Magic != file_magic::bitcod...
And I saw from the readme file thatIf your LLVM is installed in a non-standard location, first point the LLVM_CONFIG environment variable to the path of the corresponding llvm-config executable.So how can I find the location of LLVM on my computer? If I find its llvm-config executable,...