search for: langimpl4

>> Also note that the documentation is unintentionally misleading. It's very confusing for http://llvm.org/docs/tutorial/LangImpl4.html to show "Last modified: $Date: 2007-10-17 11:05:13 -0700 (Wed, 17 Oct 2007) $" at the bottom, as if nothing had changed since then, when the code it displays is actually less than a week old... I guess the source code snippets are updated automagically. As a result, the code shown th...

...-in for 94686 seems to suggest that the C bindings are somewhat preserved, but doesn't it make sense to provide some guarantees regarding the most frequently used C++ code? Also note that the documentation is unintentionally misleading. It's very confusing for http://llvm.org/docs/tutorial/LangImpl4.html to show "Last modified: $Date: 2007-10-17 11:05:13 -0700 (Wed, 17 Oct 2007) $" at the bottom, as if nothing had changed since then, when the code it displays is actually less than a week old... I guess the source code snippets are updated automagically. As a result, the code shown th...

...2010 at 8:34 AM, Christophe de Dinechin <christophe at taodyne.com> wrote: > What guarantees does LLVM try to provide regarding source code compatibility? None. > Also note that the documentation is unintentionally misleading. It's very confusing for http://llvm.org/docs/tutorial/LangImpl4.html to show "Last modified: $Date: 2007-10-17 11:05:13 -0700 (Wed, 17 Oct 2007) $" at the bottom, as if nothing had changed since then, when the code it displays is actually less than a week old... I guess the source code snippets are updated automagically. As a result, the code shown th...

On Wed, Feb 3, 2010 at 9:34 AM, Christophe de Dinechin <christophe at taodyne.com> wrote: > >>> Also note that the documentation is unintentionally misleading. It's very confusing for http://llvm.org/docs/tutorial/LangImpl4.html to show "Last modified: $Date: 2007-10-17 11:05:13 -0700 (Wed, 17 Oct 2007) $" at the bottom, as if nothing had changed since then, when the code it displays is actually less than a week old... I guess the source code snippets are updated automagically. As a result, the code shown th...

I'm working thought the Kaleidoscope tutorials for LLVM 3.3 and noticed the code listing for chapter 4 is out of date on the web. Take a look at http://llvm.org/releases/3.3/docs/tutorial/LangImpl4.html. The first line includes llvm/DerivedTypes.h, but this does not compile. The correct path is llvm/IR/Derivedtypes.h. There are other differences, and the examples that I pulled along with the source are correct. -Andy -------------- next part -------------- An HTML attachment was scrubbed...

...is wrong. Could you help me with that? I am working with the last version of LLVM (2.5). The code in chapter 2 and 3 works good, but the code in the chapter 4 did not work. Below are the detail of what I did. Regards, Juan Carlos ********************************* http://llvm.org/docs/tutorial/LangImpl4.html#jit ********************************* ./toy ready> 4+5; Segmentation fault ********************************* Details using gdb: ********************************* [New Thread 0xb7ca96c0 (LWP 9948)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7ca96c0 (LWP 9...

In http://llvm.org/docs/tutorial/LangImpl4.html#jit there's an example that optimizes calls to functions without side effects. Specifically, ready> extern sin(x); ready> extern cos(x); ready> def foo(x) sin(x)*sin(x) + cos(x)*cos(x); Read function definition: define double @foo(double %x) { entry: %calltmp = call doub...

...7 AM, Carter Cheng wrote: > > My understanding is that the JIT system allows during the running of > the system resolution of call instructions to undefined functions to > be trapped and then patched with the correct address (is this true?). Yes, see: http://llvm.org/docs/tutorial/LangImpl4.html#jit > The question I have is does the current system also allow for > repatching? for a certain OO system I am working on this could be > desirable when an object/class is updated and replaced- making it > possible in certain cases to update the call point as the code is &...

On Feb 3, 2010, at 8:34 AM, Christophe de Dinechin wrote: > Also note that the documentation is unintentionally misleading. It's very confusing for http://llvm.org/docs/tutorial/LangImpl4.html to show "Last modified: $Date: 2007-10-17 11:05:13 -0700 (Wed, 17 Oct 2007) $" at the bottom, as if nothing had changed since then, when the code it displays is actually less than a week old... I guess the source code snippets are updated automagically. As a result, the code shown th...

I've been following this guide: http://llvm.org/docs/tutorial/LangImpl4.html and am getting an error when trying to create an execution engine. When running this code: executionEngine = llvm::EngineBuilder(module).setErrorStr(&errStr).create(); errStr contains: "Interpreter has not been linked in." I'm using this command to build: g++ -g errors.o l...

...to compile it:-) The result: nada. No string is printed! (or an empty string, I should say) So more help is welcome.! Can somebody just try the code on his/her machine; maybe the tutorial is "to old" The code is, as you probably know, at: http://llvm.org/releases/2.6/docs/tutorial/LangImpl4.html#code When it is working on your system, please email me, including that version (or svn- tag/date) And I will try the same version Thanks --Groetjes, Albert ALbert Mietus GSM: +316 16 531 258 Send prive mail to: ALbert at ons-huis dot net...

My understanding is that the JIT system allows during the running of the system resolution of call instructions to undefined functions to be trapped and then patched with the correct address (is this true?). The question I have is does the current system also allow for repatching? for a certain OO system I am working on this could be desirable when an object/class is updated and replaced- making

We have been using LLVM 3.4 and are currently migrating to LLVM 3.8.1. We have been using the Old JIT and since it has been removed since 3.6, we have to use MCJIT. I find that run-time performance is very poor in 3.8.1 for the Fibonacci example in llvm/examples/fibonacci.cpp. Logs below for fib34 and fib381 for input values of 30 and 40. I first thought it could be that MCJIT compile time is

...ead tons of articles, I want to implement my own compiler and I came across a big problem. I have several questions, that I cannot answer myself: 1) If I'm writing custom compiler do I have to "hardcode" passes that it uses (like in Kaleidoscope example: http://llvm.org/docs/tutorial/LangImpl4.html) or I have to generate LLVM IR and then use the 'opt' tool to run selected passes on generated code? I think the solution with opt is not quite good, because the opt tool has to parse the LLVM IR (or BC) input file, which is not needed, because we are generating it, so we have had it i...

...vm.org/docs/tutorial/MyFirstLanguageFrontend/LangImpl5.html#for-loop-expression https://llvm.org/docs/tutorial/MyFirstLanguageFrontend/LangImpl7.html#user-defined-local-variables https://llvm.org/docs/tutorial/LangRef.html#instruction-reference https://llvm.org/docs/tutorial/MyFirstLanguageFrontend/LangImpl4.html#adding-a-jit-compiler https://llvm.org/docs/tutorial/WritingAnLLVMPass.html https://llvm.org/docs/tutorial/Passes.html https://llvm.org/docs/tutorial/ProgrammersManual.html#viewing-graphs-while-debugging-code https://llvm.org/docs/tutorial/SourceLevelDebugging.html https://llvm.org/docs/tutori...

...686 seems to suggest that the C bindings are somewhat preserved, but doesn't it make sense to provide some guarantees regarding the most frequently used C++ code? > > Also note that the documentation is unintentionally misleading. It's very confusing for http://llvm.org/docs/tutorial/LangImpl4.html to show "Last modified: $Date: 2007-10-17 11:05:13 -0700 (Wed, 17 Oct 2007) $" at the bottom, as if nothing had changed since then, when the code it displays is actually less than a week old... I guess the source code snippets are updated automagically. As a result, the code shown th...

I'm using the gvn pass, not sure about basic-aa. I've copied the code as-is from http://llvm.org/docs/tutorial/LangImpl4.html#code and added "F->addFnAttr( Attribute::ReadOnly )" after "Function *F = Function::Create(FT, Function::ExternalLinkage, Name, TheModule)". The passes it sets up are: // Set up the optimizer pipeline. Start with registering info about how the // target lays out d...

Is your compiler written in C++ or something that can interface with it easily? If so, you should probably check out the JIT, and the tutorial here: http://llvm.org/docs/tutorial/ In particular, this bit is relevant to using a JIT: http://llvm.org/docs/tutorial/LangImpl4.html#jit It sounds like you're generating LLVM IL and dumping it to a .ll file in your own compiler, so you'll probably have to just add some driver code to your compiler that drives llvm-as, opt, llvm-link, and llc. Reid On Thu, Apr 15, 2010 at 1:18 PM, Radovan Baranec <rado.baranec...

...s to suggest that the C bindings are somewhat preserved, but doesn't it make sense to provide some guarantees regarding the most frequently used C++ code? >> >> Also note that the documentation is unintentionally misleading. It's very confusing for http://llvm.org/docs/tutorial/LangImpl4.html to show "Last modified: $Date: 2007-10-17 11:05:13 -0700 (Wed, 17 Oct 2007) $" at the bottom, as if nothing had changed since then, when the code it displays is actually less than a week old... I guess the source code snippets are updated automagically. As a result, the code shown th...

...llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Rob Pieke Sent: Monday, November 15, 2010 11:41 AM To: llvmdev at cs.uiuc.edu Subject: [LLVMdev] Optimization of calls to functions without side effects (from Kaleidoscope example) In http://llvm.org/docs/tutorial/LangImpl4.html#jit there's an example that optimizes calls to functions without side effects. Specifically, ready> extern sin(x); ready> extern cos(x); ready> def foo(x) sin(x)*sin(x) + cos(x)*cos(x); Read function definition: define double @foo(double %x) { entry: %calltmp = call doubl...