search for: llvmgrep

...mpiler for our new architecture. > According to your suggestion. I try to dynamically load my backend. > But I got the error message : > llc : target 'Your_Arch' does not support static compilation! > could you tell me where is this problem? A useful tool in llvm is named 'llvmgrep'. You can use it like this: $ cd ~/llvm (or whatever) $ ./utils/llvmgrep 'does not support static compilation!' tools/llc/llc.cpp:159: << "' does not support static compilation!\n"; If you look at that file, you'll see that this is because your...

Thank you... I am preparing to build a simple C compiler for our new architecture. According to your suggestion. I try to dynamically load my backend. But I got the error message : llc : target 'Your_Arch' does not support static compilation! could you tell me where is this problem? On Mon, 24 Jan 2005 22:53:15 -0600 (CST), Chris Lattner <sabre at nondot.org> wrote: > On

I did this short experiment: ggreif at my [!297] cd /home/ggreif/llvm ggreif at my [!298] find . -name "*.cpp" | xargs grep bytecode | wc -l 143 I guess these are a quick prey for perl's in-place replace. But wait! There are more: ggreif at my [!299] find . -name "*.cpp" | xargs grep -i bytecode | wc -l 291 probably all of the rest is "Bytecode"

...liakov contributed changes to get the LLVM test suite working on FreeBSD again and is hosting a FreeBSD nightly tester. 21. Reid is now hosting a nightly tester for an optimized LLVM build (the existing Linux/X86 tester runs a debug build). Miscellaneous Changes: 22. Reid wrote the utils/llvmgrep script to make it easy to grep through the LLVM source code. 23. Reid fixed Value.h to no longer #include <iostream>. This means compiles are faster, but you will probably have to add an explicit #include to .cpp files not in CVS. 24. Reid wrote the Support/SetVector.h file, whic...

...quot;llvm" module up into three modules: > > > > * support - lib/Support, lib/System, autoconf, make support, > > utilities > > which utilities? The C++ programs in llvm/utils should not be moved. No, I was thinking more like "mkpatch" and "llvmgrep". > > > * core - VMCore, Asm, Bitcode and the essential IR tools (llvm-as, > > etc.) > > I'm still not convinced that this is useful to split out from the rest of > the LLVM tree, we should discuss this again after support is split out. Surely. Abo...

On Thu, 19 Jul 2007, Reid Spencer wrote: > With the pending reorganization of the software, I have some questions > about how developers set their PATH and LD_LIBRARY_PATH variables when > working with LLVM. This is a bit long winded, but bear with me. ok :) > We're planning to break the "llvm" module up into three modules: > > * support - lib/Support,

All, With the pending reorganization of the software, I have some questions about how developers set their PATH and LD_LIBRARY_PATH variables when working with LLVM. This is a bit long winded, but bear with me. We're planning to break the "llvm" module up into three modules: * support - lib/Support, lib/System, autoconf, make support, utilities * core - VMCore,