[all-commits] [llvm/llvm-project] 92716a: [llvm-debuginfo-analyzer] LLVM 16.0.0-rc1 Failing ...
Carlos Alberto Enciso via All-commits
all-commits at lists.llvm.org
Sun Feb 12 21:48:36 PST 2023
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 92716a42a6aa584fb009031a9f703b5dac310043
https://github.com/llvm/llvm-project/commit/92716a42a6aa584fb009031a9f703b5dac310043
Author: Carlos Alberto Enciso <carlos.alberto.enciso at gmail.com>
Date: 2023-02-13 (Mon, 13 Feb 2023)
Changed paths:
M llvm/include/llvm/DebugInfo/LogicalView/Core/LVElement.h
M llvm/include/llvm/DebugInfo/LogicalView/Core/LVStringPool.h
M llvm/include/llvm/DebugInfo/LogicalView/Core/LVSupport.h
M llvm/lib/DebugInfo/LogicalView/Core/LVSupport.cpp
Log Message:
-----------
[llvm-debuginfo-analyzer] LLVM 16.0.0-rc1 Failing test on osx-64.
As describe in
https://github.com/llvm/llvm-project/issues/60363
the following DebugInfo LogicalView Tests unit tests failed:
- ELFReader
- SelectElements
The tests fail only on the OSX-64 platform with the CMake options:
-DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON
Using the same options on a Linux platform all the tests pass:
- https://lab.llvm.org/buildbot/#/builders/196
- llvm-x86_64-debian-dylib
Basically it is a dynamic library initialization affecting a static
instance for the string pool (LVStringPool).
That string pool instance is accessed by all the logical elements
to store/retrieve any associated string during the creation of the
logical view.
For a logical view comparison, both logical readers (Reference and
Target) use retrieved indexes when comparing their strings.
Moved the static instance to LVSupport module (unnamed namespace).
Reviewed By: jmorse
Differential Revision: https://reviews.llvm.org/D143716
More information about the All-commits
mailing list