Changes

Summary

  1. Looks like XToolchainBuilder wants forward slash path separator for (details)
Commit 363234d186175c693377af5355d6f7d0d317f3f6 by gkistanova
Looks like XToolchainBuilder wants forward slash path separator for
llvm-ar path.
The file was modifiedzorg/buildbot/builders/XToolchainBuilder.py (diff)

Summary

  1. Fix build with shared libraries. NFC. (details)
  2. ARM: Don't emit R_ARM_NONE relocations to compact unwinding decoders in (details)
  3. [ObjectFileMachO] Fix the build for __arm64__. (details)
  4. [llvm-objcopy][COFF] Implement --redefine-sym and --redefine-syms (details)
  5. [LLDB][Formatters] Re-enable std::function formatter with fixes to (details)
  6. [AST] Use an explicit copy in a range-based for (details)
  7. [OpenMP] Use an explicit copy in a range-based for (details)
  8. [Analyzer] Use a reference in a range-based for (details)
  9. [CodeGen] Fix getArrayAccessFor crashes as in bug 32534 with (details)
  10. [AArch64] Fix addressing mode predicates (details)
  11. [AArch64] Update for Exynos (details)
  12. [LLDB] Always remove debugserver from LLVM_DISTRIBUTION_COMPONENTS (details)
  13. Allow additional file suffixes/extensions considered as source in main (details)
  14. [GVNHoist] Preserve AAResults. (details)
  15. [LLDB] Fix/silence CMake developer warning for LLDB framework. (details)
  16. [GlobalsAA] Restrict ModRef result if any internal method has its (details)
  17. [BPF] generate BTF_KIND_VARs for all non-static globals (details)
  18. Add -Wtautological-compare to -Wall (details)
  19. Fix include guard and properly order __deregister_frame_info. (details)
  20. [X86] Only pass v64i8/v32i16 as v16i32 on non-avx512bw targets if the (details)
  21. [X86] Don't consider v64i1 as a legal type unless v64i8 is also a legal (details)
  22. Add a shim for setenv on PS4 since it does not exist. (details)
  23. [LLDB] Remove debug message in AddLLDB.cmake (details)
  24. [LLDB] Only set FRAMEWORK when we're actually building a framework. (details)
  25. Temporarily Revert "Reapply [LVI] Normalize pointer behavior" as it's (details)
  26. Temporarily disable test. (details)
  27. [Sema] Add MacroQualified case for FunctionTypeUnwrapper (details)
  28. Don't assume that the clang binary's resolved name includes the string (details)
  29. [LLDB] Add core definition for armv8l and armv7l (details)
  30. [GlobalsAA] Reenable test. (details)
  31. AMDGPU Reduce reported maximum group size to 1024 (details)
  32. AMDGPU: Switch backend default max workgroup size to 1024 (details)
Commit ceb72d07b004af9c428c4a3c73a98ea97d49a713 by michael.hliao
Fix build with shared libraries. NFC.
- Dependent components need linking directly.
The file was modifiedllvm/examples/IRTransforms/CMakeLists.txt
Commit 1549b4699a84838c3969590dc4f757b72f39f40d by peter
ARM: Don't emit R_ARM_NONE relocations to compact unwinding decoders in
.ARM.exidx on Android.
These relocations are specified by the ARM EHABI (section 6.3). As I
understand it, their purpose is to accommodate unwinder implementations
that wish to reduce code size by placing the implementations of the
compact unwinding decoders in a separate translation unit, and using
extern weak symbols to refer to them from the main unwinder
implementation, so that they are only linked when something in the
binary needs them in order to unwind.
However, neither of the unwinders used on Android (libgcc, LLVM
libunwind) use this technique, and in fact emitting these relocations
ends up being counterproductive to code size because they cause a copy
of the unwinder to be statically linked into most binaries, regardless
of whether it is actually needed. Furthermore, these relocations create
circular dependencies
(between libc and the unwinder) in cases where the unwinder is
dynamically linked and libc contains compact unwind info.
Therefore, deviate from the EHABI here and stop emitting these
relocations on Android.
Differential Revision: https://reviews.llvm.org/D70027
The file was modifiedllvm/lib/Target/ARM/MCTargetDesc/ARMMCTargetDesc.cpp
The file was modifiedllvm/include/llvm/MC/MCELFStreamer.h
The file was modifiedllvm/test/MC/ARM/eh-compact-pr0.s
The file was modifiedllvm/lib/Target/ARM/MCTargetDesc/ARMELFStreamer.cpp
Commit 96915495f9fcbd47bf3f893200e3f5a8e30d0d9e by ditaliano
[ObjectFileMachO] Fix the build for __arm64__.
Catch up with an API change.
The file was modifiedlldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp
Commit 7af6025bd12eb086341c3076b760b053a9c2625f by maskray
[llvm-objcopy][COFF] Implement --redefine-sym and --redefine-syms
The parsing error tests in ELF/redefine-symbols.test are not specific to
ELF. Move them to redefine-symbols.test. Add COFF/redefine-symbols.test
for COFF specific tests.
Also fix the documentation regarding --redefine-syms: the old and new
names are separated by whitespace, not an equals sign.
Reviewed By: mstorsjo
Differential Revision: https://reviews.llvm.org/D70036
The file was addedllvm/test/tools/llvm-objcopy/COFF/redefine-symbol.test
The file was modifiedllvm/tools/llvm-objcopy/COFF/COFFObjcopy.cpp
The file was modifiedllvm/test/tools/llvm-objcopy/ELF/redefine-symbol.test
The file was addedllvm/test/tools/llvm-objcopy/redefine-symbols.test
The file was modifiedllvm/docs/CommandGuide/llvm-objcopy.rst
Commit 91e94a7015f14f78809e875c43acbd341d081479 by shafik
[LLDB][Formatters] Re-enable std::function formatter with fixes to
improve non-cached lookup performance
Performance issues lead to the libc++ std::function formatter to be
disabled. We addressed some of those performance issues by adding
caching see D67111 This PR fixes the first lookup performance by not
using FindSymbolsMatchingRegExAndType(...) and instead finding the
compilation unit the std::function wrapped callable should be in and
then searching for the callable directly in the CU.
Differential Revision: https://reviews.llvm.org/D69913
The file was modifiedlldb/source/Symbol/CompileUnit.cpp
The file was modifiedlldb/source/Plugins/Language/CPlusPlus/CPlusPlusLanguage.cpp
The file was modifiedlldb/source/Plugins/LanguageRuntime/CPlusPlus/CPPLanguageRuntime.cpp
The file was modifiedlldb/packages/Python/lldbsuite/test/lang/cpp/std-function-step-into-callable/TestStdFunctionStepIntoCallable.py
The file was modifiedlldb/packages/Python/lldbsuite/test/lang/cpp/std-function-step-into-callable/main.cpp
The file was modifiedlldb/include/lldb/Symbol/CompileUnit.h
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/data-formatter/data-formatter-stl/libcxx/function/TestLibCxxFunction.py
The file was modifiedlldb/source/Plugins/SymbolFile/DWARF/SymbolFileDWARF.cpp
Commit 2149028c49f8af1f3d8a9d81b2081a2b302b2d9a by koraq
[AST] Use an explicit copy in a range-based for
The AssociationIteratorTy type will be copied in a range-based for loop.
Make the copy explicit to avoid the -Wrange-loop-analysis warning.
This avoids new warnings due to D68912 adds -Wrange-loop-analysis to
-Wall.
Differential Revision: https://reviews.llvm.org/D70045
The file was modifiedclang/lib/AST/StmtPrinter.cpp
The file was modifiedclang/lib/Sema/SemaExprObjC.cpp
The file was modifiedclang/include/clang/AST/RecursiveASTVisitor.h
The file was modifiedclang/lib/Sema/SemaPseudoObject.cpp
The file was modifiedclang/include/clang/AST/ASTNodeTraverser.h
The file was modifiedclang/include/clang/AST/StmtDataCollectors.td
The file was modifiedclang/lib/Sema/TreeTransform.h
The file was modifiedclang/lib/AST/StmtProfile.cpp
Commit 51abcebbb6e5c8f8befaa523ae873adecf2d1012 by koraq
[OpenMP] Use an explicit copy in a range-based for
The std::pair<const clang::ValueDecl *,
llvm::ArrayRef<clang::OMPClauseMappableExprCommon::MappableComponent>>
type will be copied in a range-based for loop. Make the copy explicit to
avoid the -Wrange-loop-analysis warning.
This avoids new warnings due to D68912 adds -Wrange-loop-analysis to
-Wall.
Differential Revision: https://reviews.llvm.org/D70046
The file was modifiedclang/lib/CodeGen/CGOpenMPRuntime.cpp
Commit 964842861c8acd53b8df8799f7c3800c5528fb72 by koraq
[Analyzer] Use a reference in a range-based for
Let the checkers use a reference instead of a copy in a range-based for
loop.
This avoids new warnings due to D68912 adds -Wrange-loop-analysis to
-Wall.
Differential Revision: https://reviews.llvm.org/D70047
The file was modifiedclang/lib/StaticAnalyzer/Core/CheckerManager.cpp
The file was modifiedclang/include/clang/StaticAnalyzer/Core/CheckerManager.h
Commit 0aff3174dcc00516fd26c6554266b05a236166bb by llvm-project
[CodeGen] Fix getArrayAccessFor crashes as in bug 32534 with
-polly-vectorizer=polly.
Root cause is VectorBlockGenerator::copyStmt iterates all instructions
in basic block, however some load instructions may be not unnecessary
thus removed by simplification. As a result, these load instructions
don't have a corresponding array.
Looking at BlockGenerator::copyBB, it only iterates instructions list of
ScopStmt. Given it must be a block type scop in case of vectorization, I
think we should do the same in VectorBlockGenerator::copyStmt.
Patch by bin.narwal <bin.narwal@gmail.com>
Differential Revision: https://reviews.llvm.org/D70076
The file was modifiedpolly/lib/CodeGen/BlockGenerators.cpp
Commit 98856e3943de698f8c1d940c08bdbf50f04937b4 by e.menezes
[AArch64] Fix addressing mode predicates
Fix predicates related to the register offset addressing mode.
The file was modifiedllvm/lib/Target/AArch64/AArch64SchedPredicates.td
Commit 9b1e86f0cb4768a7c09b58888a86dd4be60de02e by e.menezes
[AArch64] Update for Exynos
Fix the modeling for loads and stores using the register offset
addresing mode.
The file was modifiedllvm/lib/Target/AArch64/AArch64SchedExynosM3.td
The file was modifiedllvm/lib/Target/AArch64/AArch64SchedExynosM4.td
Commit fbb228c7d222b991bed20d674e3b43143848fb95 by Jonas Devlieghere
[LLDB] Always remove debugserver from LLVM_DISTRIBUTION_COMPONENTS
Centralize the logic to remove debugserver from
LLVM_DISTRIBUTION_COMPONENTS when LLDB_USE_SYSTEM_DEBUGSERVER is
enabled. Now this happens regardless of whether the tests are enabled.
The file was modifiedlldb/test/API/CMakeLists.txt
The file was modifiedlldb/cmake/modules/LLDBConfig.cmake
Commit 335ac2eb662ce5f1888e2a50310b01fba2d40d68 by paulhoad
Allow additional file suffixes/extensions considered as source in main
include grouping
Summary: By additional regex match, grouping of main include can be
enabled in files that are not normally considered as a C/C++ source
code. For example, this might be useful in templated code, where
template implementations are being held in *Impl.hpp files. On the
occassion, 'assume-filename' option description was reworded as it was
misleading. It has nothing to do with `style=file` option and it does
not influence sourced style filename.
Reviewers: rsmith, ioeric, krasimir, sylvestre.ledru, MyDeveloperDay
Reviewed By: MyDeveloperDay
Subscribers: MyDeveloperDay, cfe-commits
Patch by:  furdyna
Tags: #clang
Differential Revision: https://reviews.llvm.org/D67750
The file was modifiedclang/tools/clang-format/ClangFormat.cpp
The file was modifiedclang/docs/ReleaseNotes.rst
The file was modifiedclang/docs/ClangFormatStyleOptions.rst
The file was modifiedclang/include/clang/Format/Format.h
The file was modifiedclang/lib/Format/Format.cpp
The file was modifiedclang/unittests/Format/FormatTest.cpp
The file was modifiedclang/unittests/Format/SortIncludesTest.cpp
The file was modifiedclang/docs/ClangFormat.rst
The file was modifiedclang/lib/Tooling/Inclusions/HeaderIncludes.cpp
The file was modifiedclang/include/clang/Tooling/Inclusions/IncludeStyle.h
Commit 4ae74cc99fb9d9c1f47cc7c5cd4c515bd53e2a19 by asbirlea
[GVNHoist] Preserve AAResults.
Resolves PR38906, PR40898.
The file was modifiedllvm/lib/Transforms/Scalar/GVNHoist.cpp
Commit a247bd1f274e49ea83b2ad39c6ff062753e9e779 by Jonas Devlieghere
[LLDB] Fix/silence CMake developer warning for LLDB framework.
This fixes the following warning for developers:
  Target 'liblldb' was changed to a FRAMEWORK sometime after install().
This
may result in the wrong install DESTINATION.  Set the FRAMEWORK
property
earlier.
The solution is to pass the FRAMEWORK flag to add_lldb_library and set
the target property before install(). For now liblldb is the only
customer.
The file was modifiedlldb/source/API/CMakeLists.txt
The file was modifiedlldb/cmake/modules/AddLLDB.cmake
Commit db69f1b22951ce49bda8e492ec8e6f60d9721668 by asbirlea
[GlobalsAA] Restrict ModRef result if any internal method has its
address taken.
Summary: If there are any internal methods whose address was taken,
conclude there is nothing known in relation of any other internal method
and a global.
Reviewers: nlopes, sanjoy.google
Subscribers: hiraditya, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D69690
The file was addedllvm/test/Analysis/GlobalsModRef/intrinsic_addressnottaken1.ll
The file was addedllvm/test/Analysis/GlobalsModRef/intrinsic_addressnottaken2.ll
The file was modifiedllvm/lib/Analysis/GlobalsModRef.cpp
The file was modifiedllvm/include/llvm/Analysis/GlobalsModRef.h
The file was addedllvm/test/Analysis/GlobalsModRef/intrinsic_addresstaken.ll
Commit 166cdc02818fd7a6653f76216b4f64cb4b21619e by yhs
[BPF] generate BTF_KIND_VARs for all non-static globals
Enable to generate BTF_KIND_VARs for non-static default-section globals
which is not allowed previously. Modified the existing test case to
accommodate the new change.
Also removed unused linkage enum members VAR_GLOBAL_TENTATIVE and
VAR_GLOBAL_EXTERNAL.
Differential Revision: https://reviews.llvm.org/D70145
The file was modifiedllvm/lib/Target/BPF/BTF.h
The file was modifiedllvm/test/CodeGen/BPF/BTF/global-var-inited.ll
The file was modifiedllvm/lib/Target/BPF/BTFDebug.cpp
Commit 9740f9f0b6e5d7d5104027aee7edc9c5202dd052 by rtrieu
Add -Wtautological-compare to -Wall
Some warnings in -Wtautological-compare subgroups are DefaultIgnore.
Adding this group to -Wmost, which is part of -Wall, will aid in their
discoverability.
Differential Revision: https://reviews.llvm.org/D69292
The file was addedclang/test/Misc/warning-wall.c
The file was modifiedclang/test/SemaCXX/warn-bitwise-compare.cpp
The file was modifiedclang/test/Sema/warn-overlap.c
The file was modifiedclang/include/clang/Basic/DiagnosticGroups.td
The file was modifiedclang/test/Sema/warn-bitwise-compare.c
Commit 38c356176b5370164578c1d08e984964354b7189 by saugustine
Fix include guard and properly order __deregister_frame_info.
Summary: This patch fixes two problems with the crtbegin.c as written:
1. In do_init, register_frame_info is not guarded by a #define, but in
do_fini, deregister_frame_info is guarded by #ifndef
CRT_HAS_INITFINI_ARRAY. Thus when CRT_HAS_INITFINI_ARRAY is not defined,
frames are registered but then never deregistered.
The frame registry mechanism builds a linked-list from the .so's static
variable do_init.object, and when the .so is unloaded, this memory
becomes invalid and should be deregistered.
Further, libgcc's crtbegin treats the frame registry as independent from
the initfini array mechanism.
This patch fixes this by adding a new #define,
"EH_USE_FRAME_INFO_REGISTRY", which is set by the cmake option
COMPILER_RT_CRT_USE_EH_FRAME_REGISTRY Currently, do_init calls
register_frame_info, and then calls the binary's constructors. This
allows constructors to safely use libunwind. However, do_fini calls
deregister_frame_info and then calls the binary's destructors. This
prevents destructors from safely using libunwind.
This patch also switches that ordering, so that destructors can safely
use libunwind. As it happens, this is a fairly common scenario for
thread sanitizer.
The file was modifiedcompiler-rt/test/crt/ctor_dtor.c
The file was modifiedcompiler-rt/lib/crt/CMakeLists.txt
The file was modifiedcompiler-rt/lib/crt/crtbegin.c
The file was modifiedcompiler-rt/CMakeLists.txt
Commit 0f04ffc073deeb1738f1d9bd5c8161d13fe42592 by craig.topper
[X86] Only pass v64i8/v32i16 as v16i32 on non-avx512bw targets if the
v16i32 type won't be split by prefer-vector-width=256
Otherwise just let the v64i8/v32i16 types be split to v32i8/v16i16.
In reality this shouldn't happen because it means we have a 512-bit
vector argument, but min-legal-vector-width says a value less than 512.
But a 512-bit argument should have been factored into the preferred
vector width.
The file was modifiedllvm/lib/Target/X86/X86ISelLowering.cpp
Commit 3e1aee2ba717529b651a79ed4fc7e7147358043f by craig.topper
[X86] Don't consider v64i1 as a legal type unless v64i8 is also a legal
type.
This avoids some nasty issues with argument passing and lowering of
arbitrary v64i8 shuffles.
The file was modifiedllvm/lib/Target/X86/X86ISelLowering.cpp
The file was modifiedllvm/test/CodeGen/X86/min-legal-vector-width.ll
Commit 7ebde1bf67daa24ea7735f2b2d7000d074e2ba93 by douglas.yung
Add a shim for setenv on PS4 since it does not exist.
A few years back a similar change was made for getenv since neither
function is supported on the PS4 platform.
Recently, commit d889d1e added a call to setenv in compiler-rt which was
causing linking errors because the symbol was not found. This fixes that
issue by putting in a shim similar to how we previously dealt with the
lack of getenv.
Differential Revision: https://reviews.llvm.org/D70033
The file was modifiedcompiler-rt/lib/profile/InstrProfilingUtil.h
Commit 34ca6e1fbef54465d623ffc8d55e824054913509 by Jonas Devlieghere
[LLDB] Remove debug message in AddLLDB.cmake
The file was modifiedlldb/cmake/modules/AddLLDB.cmake
Commit 056c3197694881379cb75a3cb1bd6a511d044714 by Jonas Devlieghere
[LLDB] Only set FRAMEWORK when we're actually building a framework.
The file was modifiedlldb/source/API/CMakeLists.txt
Commit 7a3ad48d6de0e79a92361252a815b894565b9a0f by echristo
Temporarily Revert "Reapply [LVI] Normalize pointer behavior" as it's
broken python 3.6.
Reverting to figure out if it's a problem in python or the compiler for
now.
This reverts commit 885a05f48a5d320946c89590b73a764e5884fe4f.
The file was modifiedllvm/test/Transforms/JumpThreading/combine-metadata.ll
The file was modifiedllvm/lib/Analysis/LazyValueInfo.cpp
Commit 92611da5bfc5d537e8ed69715f115a989c85769f by asbirlea
Temporarily disable test.
The file was modifiedllvm/test/Analysis/GlobalsModRef/intrinsic_addresstaken.ll
Commit e278c138a937a68f3e6c89df8eaeffa913f9b0f7 by leonardchan
[Sema] Add MacroQualified case for FunctionTypeUnwrapper
This is a fix for PR43315. An assertion error is hit for this minimal
example:
```
//clang -cc1 -triple x86_64-- -S tstVMStructRC-min.cpp int (a b)();  //
Assertion `Chunk.Kind == DeclaratorChunk::Function' failed.
```
This is because we do not cover the case in the FunctionTypeUnwrapper
where it receives a MacroQualifiedType. We have not run into this
earlier because this is a unique case where the __attribute__ contains
both __cdecl__ and
__regparm__ (in that order), and we are compiling for x86_64. Changing
the architecture or the order of __cdecl__ and __regparm__ does not
raise the assertion.
Differential Revision: https://reviews.llvm.org/D67992
The file was modifiedclang/test/Frontend/macro_defined_type.cpp
The file was modifiedclang/lib/Sema/SemaType.cpp
Commit 5ad6f279f26cd6ce77e4fa6b8df2b23be73d7beb by richard
Don't assume that the clang binary's resolved name includes the string
'clang'.
This is not true in practice in some content-addressed file systems.
The file was modifiedclang/test/Driver/arm64_32-link.c
Commit 9b958356983afffaf56788f37bdab9213369fa45 by omair.javaid
[LLDB] Add core definition for armv8l and armv7l
This patch adds core definitions in lldb ArchSpecs for armv8l and armv7l
cores.
This was needed because on Linux running on 32-bit Arm v8 we are
returned armv8l in case we are running 32-bit sysroot on 64bit kernel.
In case of 32-bit kernel and 32-bit sysroot running on arm v8 hardware
we are returned armv7l. This is quite common when we run 32 bit arm
using docker container.
Signed-off-by: Muhammad Omair Javaid <omair.javaid@linaro.org>
Differential Revision: https://reviews.llvm.org/D69904
The file was modifiedlldb/packages/Python/lldbsuite/test/make/Makefile.rules
The file was modifiedlldb/packages/Python/lldbsuite/test/lldbplatformutil.py
The file was modifiedlldb/source/Utility/ArchSpec.cpp
The file was modifiedlldb/include/lldb/Utility/ArchSpec.h
Commit 793b42a454ac12c2e437be8b8f894289e5e007b3 by asbirlea
[GlobalsAA] Reenable test.
The file was modifiedllvm/test/Analysis/GlobalsModRef/intrinsic_addresstaken.ll
Commit 25c5da5a426168b38fb3e9baa918faa75e4a92b4 by arsenm2
AMDGPU Reduce reported maximum group size to 1024
While some targets allow encoding 2048, this was never tested or
supported.
The file was modifiedllvm/lib/Target/AMDGPU/Utils/AMDGPUBaseInfo.cpp
The file was modifiedllvm/test/CodeGen/AMDGPU/attr-amdgpu-flat-work-group-size-v3.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/attr-amdgpu-flat-work-group-size.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/large-work-group-promote-alloca.ll
Commit 4b472139513ba460595804f8113497844b41fbcc by arsenm2
AMDGPU: Switch backend default max workgroup size to 1024
Previously this would default to 256, not the maximum supported size of
1024. Using a maximum lower than the hardware maximum requires language
runtimes to enforce this limit for correctness, which no language has
correctly done. Switch the default to the conservatively correct
maximum, and force frontends to opt-in to the more optimal 256 default
maximum.
I don't really understand why the changes in occupancy-levels.ll
increased the computed occupancy, which I expected to decrease. I'm not
sure if these tests should be forcing the old maximum.
The file was modifiedllvm/test/CodeGen/AMDGPU/promote-alloca-to-lds-select.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/amdgpu.private-memory.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/occupancy-levels.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/array-ptr-calc-i32.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/promote-alloca-to-lds-icmp.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/promote-alloca-to-lds-phi.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/hsa-metadata-kernel-code-props.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/promote-alloca-addrspacecast.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/private-memory-r600.ll
The file was modifiedllvm/lib/Target/AMDGPU/AMDGPUSubtarget.cpp
The file was modifiedllvm/test/CodeGen/AMDGPU/hsa-metadata-kernel-code-props-v3.ll
The file was modifiedllvm/test/CodeGen/AMDGPU/lower-range-metadata-intrinsic-call.ll

Summary

  1. Looks like XToolchainBuilder wants forward slash path separator for (details)
Commit 363234d186175c693377af5355d6f7d0d317f3f6 by gkistanova
Looks like XToolchainBuilder wants forward slash path separator for
llvm-ar path.
The file was modifiedzorg/buildbot/builders/XToolchainBuilder.py