Displaying 14 results from an estimated 14 matches for "xmemori".
Did you mean:
xmemory
2017 Apr 10
2
clang build failures using Visual Studio
Anyone run into this before?
I'm trying to get a Windows native build using Visual Studio of LLVM,
Clang, and LLD 4.0.0. So far LLVM built successfully, but I'm getting these
cryptic error messages when building Clang:
Microsoft (R) Build Engine version 15.1.1012.6693
Copyright (C) Microsoft Corporation. All rights reserved.
ClangDiagnosticsEmitter.cpp
c:\program files
2020 Jan 06
2
clang interpreter failed to materialize symbols
Hello,
I am new to LLVM and what I am trying to do is to get a very simple “hello-world” C++ program to compile to LLVM IR and then to run it using lli tool.
So here is the program code (hello.cpp):
#include <iostream>
int main (int argc, char *argv[])
{
std::cout << "Hello World!\n";
return 0;
}
Below are the steps I do to achieve that goal:
1. clang++.exe
2020 Jan 14
4
clang interpreter failed to materialize symbols
Hi Igor, not sure if that will work, but have you tried lli
-jit-kind=orc-lazy ? The default is still MCJIT:
https://github.com/llvm/llvm-project/blob/master/llvm/tools/lli/lli.cpp#L88
On 13/01/2020 19:07, David Blaikie via llvm-dev wrote:
> (+Lang for JIT/interpreter questions)
>
> On Sun, Jan 5, 2020 at 5:00 PM Igor Gomon via llvm-dev
> <llvm-dev at lists.llvm.org
2010 May 02
3
[LLVMdev] Compiling LLVM 2.7 with Visual Studio 2010.
Hey,
Downloaded the release, used CMake to create solution... building mostly
seems to be OK, except for a couple of compiler errors.
warning C4090: 'function' : different 'const' qualifiers
d:\companyone\external\llvm\source\llvm-2.7\lib\support\regengine.inc 188
error C2248: 'llvm::EquivalenceClasses<ElemTy>::ECValue::ECValue' : cannot
access private member
2010 May 02
0
[LLVMdev] Compiling LLVM 2.7 with Visual Studio 2010.
Hey,
So I tried to fix these errors, and have everything compiling now... not too
difficult, just annoying.
error C2248: 'llvm::EquivalenceClasses<
>
> ElemTy>::ECValue::ECValue' : cannot access private member declared in class
> 'llvm::EquivalenceClasses<ElemTy>::ECValue' C:\Program Files
> (x86)\Microsoft Visual Studio 10.0\VC\include\xmemory 208
2020 Jan 16
2
clang interpreter failed to materialize symbols
Hi Stefan,
I just tried the -jit-kind=orc-lazy with lli executable and it solves the problem on Ubuntu 18.04 (still does not work on Windows 10). But this solution is good enough for me now. Thanks again for your help!
--
Best Regards,
Igor
________________________________
From: Igor Gomon <giv_ua at hotmail.com>
Sent: Tuesday, January 14, 2020 7:38 PM
To: Stefan Gränitz
2014 Sep 30
2
[LLVMdev] size_t?
I'm getting compile errors because size_t is getting redefined. My
"forced include file" starts with:
#if BUILDING_FOR_WINDOWS
#define NOMINMAX
/* deal with the fact that windef.h also defines BOOL */
#define BOOL WINBOOL
#include <windows.h>
#include <intrin.h>
#undef BOOL
#endif
Looking at the preprocessor expansion of a typical .cpp file, I see that
crtdefs.h
2010 May 02
2
[LLVMdev] Compiling LLVM 2.7 with Visual Studio 2010.
Sorry for just talking to myself here, just trying to keep people in the
loop on my findings.
The problem seems to be a much larger issue with the Visual Studio 2010 C++
Compiler and not really related to clang/llvm. The following snippet of code
does *NOT *compile in 2010..
#include <vector>
int main(int argc, char* argv[])
{
std::pair<int, void*> mypair(0, NULL);
return 0;
}
2009 Jun 30
6
Variable named "memory" in templates
I tried to use a Puppet variable named "$memory" and access it from
a template, like this:
$memory = 4711
file {
"/tmp/test.txt":
content => inline_template("memory = <%= memory %>\n");
}
One would think that my file would contain "memory = 4711" after that,
but instead the memory variable seems to hold a
2014 Sep 30
2
[LLVMdev] size_t?
Hi Reid,
I copied the x64 toolsets by hand; they got installed to C:\Program
Files (x86)\LLVM\tools\msbuild\x64; they just didn't get moved correctly
by install.bat.
I just verified that the LLVM-vs2013 toolset.props is correct.
If it is a bitness problem, perhaps I'm failing to define something
correctly?
Regards,
Eric
On 9/30/14, 11:29 AM, Reid Kleckner wrote:
> This looks
2014 Oct 01
2
[LLVMdev] size_t?
I believe that we provide a definition of size_t inside the compiler itself
when clang is in MSVC compatibility mode.
On Tue, Sep 30, 2014 at 5:51 PM, Eric Mader <emader at gmx.us> wrote:
> I did some more investigation of the size_t size error. I misunderstood
> what was happening. It turns out that size_t is already defined before my
> prefix header is included. I added the
2014 Oct 01
2
[LLVMdev] size_t?
We inject a typedef for size_t here:
http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Sema/Sema.cpp?revision=218230&view=markup#l206
The typedef type is determined by calling getSizeType().
SizeType is (relevantly) calculated in two places:
X86_64
http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Basic/Targets.cpp?revision=218666&view=markup#l3512
X86_32
2012 Jun 24
2
[LLVMdev] Problems building LLVM under Visual Studio
Hi all,
I'm trying to build LLVM, synced from SVN trunk yesterday.
I ran CMake and it generated VS 2008 project files, so far so good. Then I tried to build them, by building the ALL_BUILD project.
It got the first three all right, but choked on template issues in LLVMCore:
1>------ Build started: Project: LLVMCore, Configuration: Debug Win32 ------
1>Compiling...
1>Verifier.cpp
2014 Sep 30
2
[LLVMdev] Windows Installer
I replaced all instances of "$(Platform)" with "x64" for the x64 .props
file and it still fails, so it looks like that guess was wrong as well.
Regards,
Eric
On 9/29/14, 2:11 PM, Eric Mader wrote:
> Quoting doesn't seem to make a difference. Strangely, the Win32
> toolset seems to work. (Where "work" means that clang runs and
> produces a bunch of