similar to: [LLVMdev] (Newbie) Using lli with clang++?

> $ clang++ -O3 -emit-llvm hello.cpp -c -o hello.bc > $ lli hello.bc > LLVM ERROR: Program used external function > '_ZSt16__ostream_insertIcSt11char_traitsIcEERSt13basic_ostreamIT_T0_ES6_PKS3_l' > which could not be resolved! What version of LLVM and Clang you are using? I have no such problem on my machine. Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab,

Hi, Asron > This looks relevant to me for your issue. Grabbing the cxxabi.h from there > may work: > > http://comments.gmane.org/gmane.comp.compilers.clang.devel/9391 I am not sure where to put cxxabi.h. How can I let clang find this header file while compiling LLVM and Clang (in step 2)? Thanks! Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of

Hi, I'm interested in learn how LLI works behind the scenes, that is, how interpretation and dynamic compilation works and if possible help with the development. Is there any documentation regarding specifically this part of the system? I've read some general documentation: prog. manual, lang. reference, ... Any advice on what start reading will be very welcome. César.

+ LLVM-dev (clang is mostly about the frontend and this is a backend failure), you may have more change to get an answer. > On Feb 6, 2017, at 5:49 AM, Gaetano Checinski via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > Running the following code with clang++ -S -emit-llvm main.cpp && lli main.ll on Linux(Debian) > > #include <future> > > int main () {

On Sat, Jul 30, 2011 at 2:35 AM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi, Asron > > > This looks relevant to me for your issue. Grabbing the cxxabi.h from > there > > may work: > > > > http://comments.gmane.org/gmane.comp.compilers.clang.devel/9391 > > I am not sure where to put cxxabi.h. How can I let clang find this > header file while

> I’ve seen the same problem, but didn’t find solution back then. > I can give a hint that it is related to a thread local storage (notice TLS in the name). > > The same result can be reproduced by this simple program: > > thread_local int x = 0; > int main() { > return 0; > } > >When compiled into IR it produces similar error: > >LLVM ERROR:

Hi, Aaron > > I am not sure where to put cxxabi.h. How can I let clang find this > > header file while compiling LLVM and Clang (in step 2)? > > > > You need to add it to somewhere that is in Clangs includes search path. E.g. > $INSTALL/lib/clang/2.9/include perhaps. Thanks for your help. Now I have another problem, --- llvm[4]: Compiling Version.cpp for Release

Linking lli debug executable (without symbols) /mounts/zion/disks/0/localhome/pmeredit/llvm/lib/Debug/lli-interpreter.o(.te xt+0x643a): In function `llvm::Interpreter::callExternalFunction(llvm::Function*, std::vector<llvm::GenericValue, std::allocator<llvm::GenericValue> > const&)': /localhome/pmeredit/llvm/lib/ExecutionEngine/Interpreter/ExternalFunctions.c pp:98: undefined

On Thu, Feb 07, 2013 at 11:09:10AM +0100, Óscar Fuentes wrote: > Blind Faith <person.of.book at gmail.com> writes: > > > I used the LLVM demo page http://llvm.org/demo/ to generate C++ code for > > generating LLVM IR code. But that page is now disabled. Is there any tool > > or other site which does what I'm trying to do, that is I give "C/C++ code"

Hi all, I am running LNT with LLVM/Clang 3.0 Release binary and test suite, here is my flow (most of them are the same as http://llvm.org/docs/lnt/quickstart.html). --- $ svn co http://llvm.org/svn/llvm-project/lnt/trunk ~/lnt $ ~/mysandbox/bin/python ~/lnt/setup.py develop $ cd mysandbox; source bin/activate $ $ lnt runtest nt \ --sandbox SANDBOX \ --cc

> >  But I got the error message below, > > > > --- > > 2012-04-12 02:39:48: executing test modules > > 2012-04-12 02:39:49: loading nightly test data... > > nt.py:737: fatal error: nightly test failed, no report generated > > --- > > > >  Any idea on how I can figure out what the fatal error is? Thanks! > > Inside the sandbox there will

On Fri, Jul 8, 2011 at 9:30 AM, Karel Gardas <karel.gardas at centrum.cz> wrote: > On 07/ 8/11 05:26 PM, Eli Friedman wrote: >> >> Given that revision range, the only remotely likely culprit is 131463. >>  Which basically means that it "broke" because the default target >> features changed. > > And you are right here. 131463 == 131464 which is

On 07/ 8/11 05:26 PM, Eli Friedman wrote: > Given that revision range, the only remotely likely culprit is 131463. > Which basically means that it "broke" because the default target > features changed. And you are right here. 131463 == 131464 which is buggy. 131462 is OK. Thanks, Karel

Could you tell me the current status of MIPS JIT? On Mon, Apr 30, 2012 at 11:38 PM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > > Thanks for your information. > > Could you suggest any other framework that I could use for making a > custom JIT > > for ARM? > > I am doing research on JIT compilation for a heterogeneous processor > system. > > If not for

On Wed, Apr 11, 2012 at 7:59 PM, 陳韋任 <chenwj at iis.sinica.edu.tw> wrote: > Hi all, > >  I am running LNT with LLVM/Clang 3.0 Release binary and test suite, here is my > flow (most of them are the same as http://llvm.org/docs/lnt/quickstart.html). > > --- > $ svn co http://llvm.org/svn/llvm-project/lnt/trunk ~/lnt > $ ~/mysandbox/bin/python ~/lnt/setup.py develop >

Hi everyone, Recently I tried to compile llvm-gcc-4.2-2.9 on a 64bit ubuntu12.04 machine. And I was using the settings below, export C_INCLUDE_PATH=/usr/include/x86_64-linux-gnu export LIBRARY_PATH=/usr/lib/x86_64-linux-gnu ../llvm-gcc-4.2-2.9.source/configure --enable-optimized --program-prefix=llvm- --enable-checking --enable-llvm=${HOME}/moonbox/llvm-obj/Debug+Asserts

On Tue, May 01, 2012 at 11:11:44AM +0900, Toan Mai wrote: > Could you tell me the current status of MIPS JIT? According to [1], the support for "old-style" JIT is complete. You can give it a shot. > I'm afraid it's not straightforward to fix it, Chen. Well, no pain no gain. ;) Regards, chenwj [1] http://llvm.org/releases/3.0/docs/ReleaseNotes.html#whatsnew --

On Feb 7, 2013, at 6:26 PM, 陳韋任 (Wei-Ren Chen) <chenwj at iis.sinica.edu.tw> wrote: > On Thu, Feb 07, 2013 at 11:09:10AM +0100, Óscar Fuentes wrote: >> Blind Faith <person.of.book at gmail.com> writes: >> >>> I used the LLVM demo page http://llvm.org/demo/ to generate C++ code for >>> generating LLVM IR code. But that page is now disabled. Is there

Hi, Does anyone know which version of LLVM support "opt --insert-block-profiling command"? Thanks! Jianing Zhao On Apr 14, 2012, at 8:08 AM, Duncan Sands wrote: > Hi Jianing Zhao, > >> When I use the opt --insert-block-profiling command, there is " opt: Unknown command line argument '-insert-block-profiling'." > > yes, it doesn't exist any

On Wed, Sep 19, 2012 at 12:42:18AM +0000, Kaylor, Andrew wrote: > It seems to me that MCJIT would be a nice default on the platforms that support it. On the other hand, I don't like the idea of the default behavior being platform dependent. > > Perhaps the biggest obstacle to changing the default is that it would have complicated implications for the automated tests. The testing of