similar to: [LLVMdev] Tool for run-time code generation?

I happen to be using LLVM for just this reason. I process large volumes of data records with schemas that are only known at runtime and/or can change dynamically as various transforms are applied to such records at various stages. To this end, I auto-generate C99 syntax at run time, parse it using clang, do some AST transformations, compile using LLVM JIT, and then execute within the same (C++)

Martin C. Martin wrote: > > > On 7/16/2010 10:30 PM, Nick Lewycky wrote: >> Vlad wrote: >> >> Instead, break the chunks of C you would generate into functions and >> compile those ahead-of-time. At run time you use llvm only (no clang) to >> generate a series of function calls into those functions. > > Compelling. I hadn't considered that. > >

On 7/17/2010 12:38 PM, Nick Lewycky wrote: > Martin C. Martin wrote: >> >> >> On 7/16/2010 10:30 PM, Nick Lewycky wrote: >>> Vlad wrote: >>> >>> Instead, break the chunks of C you would generate into functions and >>> compile those ahead-of-time. At run time you use llvm only (no clang) to >>> generate a series of function calls

> > What's wrong with running LLVM on ARM? > > LLVM can generate code for ARM, but the JIT requires extra target and > platform dependent stuff, and that's not done for arm-wince. The release notes say "compiler_rt now supports ARM targets". What else is needed? Keep in mind that I do not need (or want) Clang or any of the optimizers: I just want to generate

> LLVM has a JIT for this purpose. You generate LLVM IR code (a sort of > generic assembler) and it produces optimized native code ready to be > executed. > > x86-win32 is fine. I don't think so about arm-wince. What's wrong with running LLVM on ARM? It's supposed to support ARM as a target, and since it's written in C it should theoretically compile for ARM. CMake

Vlad wrote: > I happen to be using LLVM for just this reason. I process large volumes > of data records with schemas that are only known at runtime and/or can > change dynamically as various transforms are applied to such records at > various stages. > > To this end, I auto-generate C99 syntax at run time, parse it using > clang, do some AST transformations, compile using LLVM

On Wed, Jul 28, 2010 at 9:01 AM, David Piepgrass <dpiepgrass at mentoreng.com> wrote: >> A LLVM JIT compiler for x86 under 1 MB? I doubt it is possible without >> a major rewriting of LLVM. > > Even with no optimizations? Drat. That means I can't use it. Why? I'd never checked, but I always assumed the LLVM JIT was much larger than 3.4 MB. For comparison: [rnk at

Trevor Harmon <Trevor.W.Harmon at nasa.gov> writes: > On Jul 23, 2010, at 10:24 AM, David Piepgrass wrote: > >> The top ten LLVM libraries (Win32 *.lib) are pretty huge: >> >> Release Bld Debug Bld Name >> 24,510,490 71,038,240 LLVMCodeGen.lib [snip] > Not sure about Win32, but here are some numbers on OS X for comparison: > > 5,282,356

----- Original Message ---- > From: David Piepgrass <dpiepgrass at mentoreng.com> > To: Óscar Fuentes <ofv at wanadoo.es> > Cc: "LLVMdev at cs.uiuc.edu" <LLVMdev at cs.uiuc.edu> > Sent: Fri, July 16, 2010 2:22:57 PM > Subject: Re: [LLVMdev] Tool for run-time code generation? > > > > What's wrong with running LLVM on ARM? > > >

> Have you ever tried running a dynamically allocated code that cannot > execute > malloc() or any runtime libraries or library-based functions because > they haven't been ported to your architecture? That's what it would > be like trying to run ARM Linux code on your WinCE target. Windows CE > requires an LLVM port before it will be useful to you. Put simply,

> > On Jul 23, 2010, at 10:24 AM, David Piepgrass wrote: > > > >> The top ten LLVM libraries (Win32 *.lib) are pretty huge: > >> > >> Release Bld Debug Bld Name > >> 24,510,490 71,038,240 LLVMCodeGen.lib > [snip] > > Not sure about Win32, but here are some numbers on OS X for > comparison: > > > > 5,282,356

David Piepgrass <dpiepgrass at mentoreng.com> writes: >> LLVM has a JIT for this purpose. You generate LLVM IR code (a sort of >> generic assembler) and it produces optimized native code ready to be >> executed. >> >> x86-win32 is fine. I don't think so about arm-wince. > > What's wrong with running LLVM on ARM? LLVM can generate code for ARM,

> Why do you care about the size of library files? I assumed dynamic libraries and static libraries were similar in size, but I just checked some of my own static libraries and they are indeed much larger than the executables they compile to. Sorry, it just never occurred to me that they would be much different. > > Anyway, in the same example I mentioned that the size of HowToUseJIT

David Piepgrass <dpiepgrass at mentoreng.com> writes: > Using C++ code, I would like to generate code at run-time (the same > way .NET code can use dynamic methods or compiled expressions) in > order to obtain very high performance code (to read binary data > records whose formats are only known at run-time.) > > I need to target x86 (Win32) and ARM (WinCE). > > Can

David Piepgrass <dpiepgrass at mentoreng.com> writes: >> Comparing the size of the static libraries makes little sense, and even >> less when they are compiled by different tools. What really matters is >> the size of the executables. >> >> I agree that LLVM can be considered a heavyweight dependency on this >> aspect. > > Why is the size of static

I constructed an LLVM 2.7 VS solution with cmake, but it has 66 projects: ALL_BUILD, ".\ALL_BUILD.vcproj" BrainF, "examples\BrainF\BrainF.vcproj" Fibonacci, "examples\Fibonacci\Fibonacci.vcproj" FileCheck, "utils\FileCheck\FileCheck.vcproj" HowToUseJIT,

One thing that helps me understand complex software is a dependency graph. I found an LLVM dependency graph at https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies but it's really messy and hard to follow. From that graph I made a cleaner graph by hand (attached)... sorry about the fax-quality scan. But I have some questions about it... -

----- Original Message ---- > From: David Piepgrass <dpiepgrass at mentoreng.com> > To: Samuel Crow <samuraileumas at yahoo.com> > Sent: Fri, July 16, 2010 2:48:10 PM > Subject: RE: [LLVMdev] Tool for run-time code generation? > > WinCE offers most of the standard C APIs (such as malloc), as well as most >standard C++ libraries including, I think, the same STL

Hi, Found a nice little video about a prototype phone from broadcom currently sitting in Microsoft WinCE lab. The video is at: http://channel9.msdn.com The video in question is an interview with Mike Hall titled "Windows CE and Windows Embedded Lab Tour". The clip dealing with the VOIP phone is right at the start so you don't need to watch the whole thing (although there is some

Hello Friends, I am trying to use speex-1.2beta3 version for echo cancelling. On my WinCE board I am using WaveIn/WaveOut functions to record and playback audio. I am receiving audio data on udp socket, then playing it on speaker using WaveOutWrite function. I registered callback to capture microphone data, then data chunk came from socket ( which I played on speaker) and data captured from