similar to: llvm 5.0.1 requires downstream workaround for diaguids.lib

Displaying 12 results from an estimated 12 matches similar to: "llvm 5.0.1 requires downstream workaround for diaguids.lib"

2018 Jan 23
1
[PDB] Error "DIA is not installed on the system" occured in `llvm::pdb::loadDataForExe()`.
Hi all, I have two questions about reading PDB file. For `llvm::pdb::loadDataFromEXE(PDB_ReaderType Type, ...)`, there are two places calling this method, `LLVMSymbolizer::getOrCreateModuleInfo(PDB_ReaderType::DIA, ...)`, see https://github.com/llvm-mirror/llvm/blob/master/lib/DebugInfo/Symbolize/Symbolize.cpp#L403, and `SymbolFilePDB::CalculateAbilities(PDB_ReaderType::DIA, ...)`, see
2018 Jan 23
0
MachineVerifier and undef
Thanks Krzysztof. That's very helpful - I was missing the distinction between a register containing an undefined value and a register marked as containing an undefined value. Cheers! On 1/23/18, via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Send llvm-dev mailing list submissions to > llvm-dev at lists.llvm.org > > To subscribe or unsubscribe via the World Wide Web,
2018 May 16
0
Compile error while building LLDB
+ Jonas who hit the same bug recently. On Wed, May 16, 2018 at 8:01 AM, Eric Gorr via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I was just trying to build lldb-6.0 from source (and had previously > successfully build llvm-6.0, clang-6.0, and lld-6.0 from source), but > received a compile error while using both just cmake and cmake+ninja > > Does this look familiar to
2018 May 16
2
Compile error while building LLDB
I was just trying to build lldb-6.0 from source (and had previously successfully build llvm-6.0, clang-6.0, and lld-6.0 from source), but received a compile error while using both just cmake and cmake+ninja Does this look familiar to anyone? In file included from llvm/lldb-6.0.0.src/source/API/SystemInitializerFull.cpp:89: In file included from
2018 May 26
0
Compile error while building LLDB
Sounds like we have an issue in the CodeView headers related to a duplicate symbol. While this doesn't entirely surprise me after seeing the error, I'm also not sure why this problem is only just happening now. Ultimately what's happening is we have this enumeration: enum class RegisterId : uint16_t { ... CR3, ... }; But your termios.h file also has a #define for CR3. I guess one
2018 May 16
2
Compile error while building LLDB
I'm still trying to figure this out. On one of my machines it went away after a clean install even though my configuration is exactly the same. I'll let you know once I know more. On Wed, May 16, 2018 at 5:28 PM Davide Italiano <davide at freebsd.org> wrote: > + Jonas who hit the same bug recently. > > On Wed, May 16, 2018 at 8:01 AM, Eric Gorr via llvm-dev >
2015 Nov 14
2
(no subject)
Hello all! Please forgive me if this is the wrong mailing list for my question. First off, I am on Windows and using git bash for everything: $ uname MINGW32_NT-6.2 I am attempting to essentially do the kalidescope example. I have copied the code verbatim from the full code listing and am running the following command: $ clang-cl toy.cpp deps/llvm/build/Debug/lib/*.lib //MDd -o toy.exe -I
2015 Jun 19
4
[LLVMdev] [CMake] Generated LLVMConfig.cmake and LLVMExports.cmake broken under Visual Studio 2015
On 06/18/2015 06:46 PM, Dan Liew wrote: >> The issue is the that that generated LLVMExports.cmake file has this in it >> INTERFACE_LINK_LIBRARIES "LLVMObject;LLVMSupport;C:\Program Files (x86)\Microsoft Visual Studio 14.0\DIA SDK\lib\diaguids.lib" > > Hmm actually this might be a bug in the > ``/lib/DebugInfo/PDB/CMakeLists.txt`` file. CC'ing Zach Turner seeing
2015 Jun 18
2
[LLVMdev] [CMake] Generated LLVMConfig.cmake and LLVMExports.cmake broken under Visual Studio 2015
Hi, Myself and a colleague of mine are trying to use LLVM's exported targets [1] on trunk and I've noticed that the generated CMake files (LLVMConfig.cmake and LLVMExport.cmake) are broken when trying to use Visual Studio 2015 (using CMake 3.2.1). ## Broken target properties in LLVMExports.cmake LLVM itself builds fine but when our project tries to do ``find_package(LLVM)`` we get the
2016 Oct 19
2
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
The new error message is: llvm-pdbdump: DIA Error: An unknown error has occurred. HRESULT: 0x800700C1: Calling NoRegCoCreate which is more or less what I expected. The specific HResult is kind of interesting, it maps to "msdia140.dll is not a valid Win32 application". I don't know if this means that it can't find the DLL, or that it did find the DLL and it's corrupt. Is
2017 Oct 25
2
linkonce expected behavior?
On Tue, Oct 24, 2017 at 9:27 PM, Vedant Kumar <vsk at apple.com> wrote: > Unreferenced linkonce globals are allowed to be discarded. > > > Is __udivmodti4 referenced? > It's referenced by a different .o file, but nothing within the module. My confusion comes from the missing direct object in the sentence. Referenced by a function local to the module? Referenced by any
2016 Oct 19
2
[cfe-dev] Revisiting our informal policy to support two versions of MSVC
We can try to print a better error message here, but it looks like regardless someone will need physical access to the bot to determine what the problem is with DIA. On Wed, Oct 19, 2016 at 8:51 AM Reid Kleckner <rnk at google.com> wrote: > I filed https://llvm.org/bugs/show_bug.cgi?id=30736 to get that fixed. > > On Wed, Oct 19, 2016 at 3:52 AM, Briltz, Denis <Denis.Briltz at