search for: piepgrass

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 w...

...unt of effort required to figure things out in both clang and LLVM codebases. For example, how to traverse or mutate ASTs produced by clang is pretty much a FAQ on the clang list but there is no good documentation addressing this very common use case. HTH, Vlad On Jul 16, 2010, at 10:47 AM, David Piepgrass wrote: > 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...

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 libLLVMCodeGen.a...

...ance code (to read binary data records whose formats are only known at run-time.) I need to target x86 (Win32) and ARM (WinCE). Can LLVM be used for this purpose, or would something else work better? Are there any open-source projects that have done this, that I could look to as an example? David Piepgrass, E.I.T. Software Developer __________________________________________ Mentor Engineering Inc.<http://www.mentoreng.com/> 10, 2175 - 29th Street NE Calgary, AB, Canada T1Y 7H8 Ph: (403) 777-3760 ext. 490 Fax: (403) 777-3769 What are the costs of speeding & idling in your fleet? Watch...

I am considering using LLVM in a project for a Windows CE where space is at a premium. My jaw dropped when I checked the size of HowToUseJIT.exe (VC++ Win32 debug): 15.4 MB! The release build of HowToUseJIT is "only" 3.39 MB, but this is still 85% larger than the binary to which I was thinking of adding LLVM. The top ten LLVM libraries (Win32 *.lib) are pretty huge: Release Bld Debug

On Jul 26, 2010, at 9:41 AM, David Piepgrass wrote: > Based on cmake/modules/LLVMLibDeps.cmake, I produced a graphviz dot file and then manually removed components and edges until the graph was small enough to be presentable. I don’t know if I can actually use LLVM due to its humongousness, but I hope the graph will be helpful to others a...

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 > 21,084,666 56,724,338 LLVMCore.lib > 14,624,218 37,070,488 LLVMAnalysis.lib > 11,987,202 30,711,450 LLVMScalarOpts.lib &gt...

> > 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...

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...

> > 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

> 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

...s out in both clang > and LLVM codebases. For example, how to traverse or mutate ASTs produced > by clang is pretty much a FAQ on the clang list but there is no good > documentation addressing this very common use case. > > HTH, > Vlad > > On Jul 16, 2010, at 10:47 AM, David Piepgrass wrote: > >> 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...

...only the archive form is shown." Are "archive library" and "object library" the names Unix uses for dynamic link libraries and static libraries? What difference does it make to the dependency graph whether a library is "archive" or "object"? From: David Piepgrass Sent: Wednesday, July 21, 2010 4:16 PM To: 'llvmdev at cs.uiuc.edu' Subject: Is there a guide to LLVM's components? I constructed an LLVM 2.7 VS solution with cmake, but it has 66 projects: ALL_BUILD, ".\ALL_BUILD.vcproj" BrainF, "example...

Based on cmake/modules/LLVMLibDeps.cmake, I produced a graphviz dot file and then manually removed components and edges until the graph was small enough to be presentable. I don't know if I can actually use LLVM due to its humongousness, but I hope the graph will be helpful to others attempting to comprehend LLVM. PNG attached; dot file follows. digraph G { ipo

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...

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. &g...

----- 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+...

----- 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 wro...

> 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

> 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,