similar to: RFC: Adding IR Transformation examples/tutorial code to llvm-project

Am Fr., 25. Okt. 2019 um 17:32 Uhr schrieb Florian Hahn <florian_hahn at apple.com>: >> 2.Chris Bieneman seeks to simplify the cmake build system, including >> significantly reducing the number of configuration parameters and >> making "make all" really make everything, including examples. This >> would make the overall configure process slower even when not

On Fri, Oct 25, 2019 at 2:43 PM Michael Kruse via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I like the idea and already discussed it with Kit Barton. > > Two concerns that I had: > > 1. Keeping them in-tree requires them to be up-to-date, a potential > additional maintenance burden. This might be what we want, but I get > less enthusiastic when thinking about

Now I have -DLLVM_INCLUDE_EXAMPLES:BOOL=OFF but Kaleidoscope is still there and selected for build (-G "Visual Studio 9 2008") -Jochen

>> Now I'm using LLVM_BUILD_EXAMPLES=OFF and I have >> >> //Build LLVM example programs. >> LLVM_BUILD_EXAMPLES:BOOL=OFF >> >> in the cmakecache.txt file but it also does not seem to >> work. >> > > What that means? LLVM_BUILD_EXAMPLES shall create build targets for the > examples but do not build them when you build the ALL_BUILD

Jochen Wilhelmy <j.wilhelmy at arcor.de> writes: > is it possible to build only the libs (and no executables) with cmake? > I already have LLVM_BUILD_TOOLS:BOOL=OFF > and CLANG_BUILD_EXAMPLES:BOOL=OFF but things like Kaledoscope > are still built. LLVM_BUILD_EXAMPLES=OFF http://www.llvm.org/docs/CMake.html#llvmvars

Hi! is it possible to build only the libs (and no executables) with cmake? I already have LLVM_BUILD_TOOLS:BOOL=OFF and CLANG_BUILD_EXAMPLES:BOOL=OFF but things like Kaledoscope are still built. -Jochen

Hi, I am building a new JIT compiler for Lua (actually a derivative of Lua), and am planning to use LLVM for this. I have trying out some basic functions using LLVM 3.5.1. I have been puzzled by one aspect of the MCJIT versions of the Kaleidoscope sample, and would hugely appreciate some insight. Can a single MCJIT instance be used to manage several modules? Why is a separate MCJIT instance

Sorry to trouble you, great software, I have it on Ubuntu 14.10, Windows 10 and now I was trying ARM: I have been trying to build a working Cland+LLVM for 4 days now, ARM Radxa Rock Pro Quad 1.6Ghz 2GB memory I'm building on an SD card, I tried 4GB and died(space thing), 8GB and died(again with the space thing) so I read everything I could find on building only a minimum testing build and I

On Tue, Apr 21, 2015 at 7:26 AM, Per Mildner <Per.Mildner at sics.se> wrote: > Charlie Turner <charlesturner7c5 <at> gmail.com> writes: > > > I was planning on committing these changes with the corresponding > > changes to the Kaleidoscope tutorial walk-through. Might be a bit of a > > surprise to have no explanation of what MCJITHelper and friends is

Hi all, I tried to modify Kaleidoscope Tutorial (toy.cpp from llvm/examples/Kaleidoscope/Chapter7, LLVM 3.3 release branch) in order to use MCJIT instead of JIT. I get segmentation fault when running toy.cpp with fibonacci example from the tutorial. My modified toy.cpp is in attachment and still works with JIT (when #define USE_MCJIT line is commented out). I read discussions regarding

Hi, I am looking to port my MCJIT based implementation to ORC. I have been reading up on the ORC tutorials, but am not clear on how to do following: I would like to discard everything other than the compiled code after compiling a module. A module may have more than one function in it - so I would like to retain all the compiled functions. I am okay with eager compilation - i.e. there is no need

Hello I've been looking to LLVM, in order to develop a compiler for a cryptography oriented language. I started by following the tutorials on Kaleidoscope, and I must say they were very usefull. Now I need to use GMP, so i can add Big Integer support. I am trying to change Kaleidoscope to support BigIntegers instead of doubles, but I don't really know how to do that. I'd really

I try to understand cmake build configuration. As an example, I copied Kaleidoscope from llvm examples to some other directory (e.g., /tmp/Kaleidoscope). What change(s) that I need to make to "CMakkeLists.txt" in order to build Kaleidoscope from /tmp/Kaleidoscope? Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Tue, Apr 21, 2015 at 3:07 PM, Lang Hames <lhames at gmail.com> wrote: > No progress since Charlie last looked at it. Sorry, I meant to refer to the issue Per Mildner mentioned regarding the tutorials not building due to RTTI - which I recall discussing with you & Eric, but don't know what came of it. > As Per suggested, it may be > worth adding an explicit #error, or at

Hi, On 22 September 2017 at 15:33, Dibyendu Majumdar <mobile at majumdar.org.uk> wrote: > I am looking to port my MCJIT based implementation to ORC. I have been > reading up on the ORC tutorials, but am not clear on how to do > following: > > I would like to discard everything other than the compiled code after > compiling a module. > A module may have more than one

Am 04.06.2013 16:05, schrieb David Tweed: > | I am curious about JMM->invalidInstructionCache(), which I found in > | lli.cpp implementation. lli.cpp contains also call finalizeObject(), I > | just overlooked it. lli.cpp calls finalizeObject(), which calls > | applyPermissions, which in turn calls invalidateInstructionCache. So why > | lli.cpp does call

Lang, I added the add/get global mapping to my kaleidoscope JIT, but I think perhaps these would make more sense if they were added to the object linking layer as they would be generally usable there. On Aug 19, 2015, at 11:19 PM, Andy Somogyi wrote: > Hey Lang, > > I've added this to my Kaleidoscope JIT, and it seems to work just fine, basically I copied the global mapping

Hi I’ve previously used the ExecutionEngine::addGlobalMapping to make existing functions available to my JITed code. I’m currently using ORC, as MCJIT does not appear to be maintained any longer (the kaleidoscope examples have not worked for some time with MCJIT). I’m using just the basic ORC CompileLayer directly. So, I’ve essentially copied the ExecutionEngine::addGlobalMapping related

Hi Andy, I think that makes sense. I'm currently rewriting the core Kaleidoscope tutorials - I'll look at adding support for this. - Lang. On Fri, Aug 14, 2015 at 7:38 AM, Andy Somogyi <andy.somogyi at gmail.com> wrote: > After some fiddling with it, it does in fact look like it works as you > describe Lang. > > The trick was you had to call > >

Hi llvm-admin, (cc llvm-dev for visibility) We’re working on some improvements to the documentation, and want to move things (e.g. the Kaleidoscope tutorial into a subdirectory) around without breaking any links to it. Is there a way to do forwards on the web page that you prefer? -Chris