similar to: [LLVMdev] llvm-config "to do" list

Change your g++ build to: g++ -g -O0 toy-example26.cpp -o toy-example26 `/Users/albert/NoTimeMachine/LLCM_Clang/llvm-trunk/BUILD/Debug/bin/llvm-config --cppflags --ldflags --libs core jit interpreter native` After you get this working, try it with the source interpreter include removed, and minus the above interpreter llvm-config addition. Garrison On Jan 23, 2010, at 18:55, ALbert Mietus

--Groetjes, Albert ALbert Mietus GSM: +316 16 531 258 Send prive mail to: ALbert at ons-huis dot net Don't send spam mail! Mijn missie: http://SoftwareBeterMaken.nl product, proces & imago. Mijn leven in het kort: http://albert.mietus.nl/Doc/CV_ALbert.html On 23 Jan 2010., at 22:07, Garrison Venn wrote: > Look

On Thu, 2006-03-23 at 00:58 -0500, Eric Kidd wrote: > On Mar 22, 2006, at 11:22 PM, Reid Spencer wrote: > > LLVM back end target library (LLVM IR -> machine code). > > What would you include in each set? I dunno. You want me to actually think about this stuff? :) I'd have to derive the actual set of required libraries, but I'm lacking motivation for that task right

On Mar 23, 2006, at 1:22 AM, Reid Spencer wrote: > I dunno. You want me to actually think about this stuff? :) > > I'd have to derive the actual set of required libraries, but I'm > lacking > motivation for that task right now. OK, here's my current minimalist proposal: backend: Either a native backend or a C backend. engine: Enough libs to run ExecutionEngine

Hi Eric, Its definitely amusing :) About the only thing I can suggest are: 1. Combine LLVMSparc*.o into one LLVMSparc.a. That work is already happening with the new Sparc backend that is being developed. Should be out in 1.7 (Chris?) 2. Combine the JIT/Interpreter/ExecutionEngine into one .a I don't know enough about the codegen/target/analysis/ipa stuff to be able to make any

On Tue, 21 Mar 2006, Reid Spencer wrote: > About the only thing I can suggest are: > > 1. Combine LLVMSparc*.o into one LLVMSparc.a. That work is already > happening with the new Sparc backend that is being developed. Should be > out in 1.7 (Chris?) I wouldn't worry about the SparcV9 backend for your project. > 2. Combine the JIT/Interpreter/ExecutionEngine into one .a

On Mar 24, 2006, at 1:37 AM, Chris Lattner wrote: > On Thu, 23 Mar 2006, Eric Kidd wrote: >> backend: Either a native backend or a C backend. >> engine: Enough libs to run ExecutionEngine using either a JIT or >> interpreter. >> all: All LLVM libraries. >> >> Please feel free to suggest better names. :-) > > Instead of 'engine', how about

On Mar 16, 2006, at 2:16 AM, Chris Lattner wrote: > On Wed, 15 Mar 2006, Eric Kidd wrote: >> OK! Would something like the following interface be a reasonable >> first approach? >> >> llvm-config (--cxxflags | --ldflags | --libs) (all | jit) >> --cxxflags: Flags to use when compiling C++ source code. >> --ldflags: Linker flags to use when linking

Hi all! I have installed LLVM 1.9 under FreeBSD and read the documentation. Problem: examples/HowToUseJIT fails to compile. I entered the following command in the directory /usr/home/x/llvm1.9/examples/HowToUseJIT : gmake ENABLE_OPTIMIZED=0 It stops after producing object files (.o) without comment. When I enter the following (from the documentation): g++ `llvm-config --ldflags` -o HowToUseJIT

The only thing that comes to me off the top of my head is to look at the various LLVM tools and applications and see if there are common sets of libraries used by the tools. Ideally we'd want to "llvm-config --libs {toolname}" for each tool where {toolname} is replaced by the virtual component corresponding to the tool. That might be overkill, but if there are multiple tools that

Reid added some nice inter-library dependency data to utils/llvm- config/LibDeps.txt. There are three sets of circular dependencies between LLVM libraries. If you use any library from one of these sets, you may need to pull in the rest: LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a libLLVMTransformUtils.a libLLVMipa.a LLVMSparcV9.o LLVMSparcV9InstrSched.o

On Mar 22, 2006, at 11:22 PM, Reid Spencer wrote: > In looking at tools, we should also look at the example programs > and the > projects such as Stacker. For example, it would be nice to have a > virtual component that includes the libraries necessary for an LLVM > front end translator (source -> llvm bytecode). It would also be nice > to have a virtual component that

On Thu, 23 Mar 2006, Eric Kidd wrote: >> I'd have to derive the actual set of required libraries, but I'm lacking >> motivation for that task right now. > > OK, here's my current minimalist proposal: > > backend: Either a native backend or a C backend. > engine: Enough libs to run ExecutionEngine using either a JIT or > interpreter. > all: All LLVM

You can get help on the whole package by > help(package="multtest") which is likely pretty close to what you want. There's the index etc for the package on the web as well. You can also just look in the package's installation directory. If it's loaded you can do an ls(2) say if it loaded in position 2, to get all objects in the package. Reid -----Original Message-----

LLVM 1.7 is available now! Download it here: http://llvm.org/releases/ Release notes here: http://llvm.org/releases/1.7/docs/ReleaseNotes.html This release is huge! It contains about twice the number of new features as any previous release, and includes some big-ticket items that people have been requesting for a long time. In particular, this release contains a completely rewritten llvm-gcc

To ease portability headaches, I'd like to support several virtual "components" in llvm-config. Possibilities include: all: Include all LLVM libraries. backend: Include either a working native backend or cbackend. engine: Include a working subclass of ExecutionEngine, either the JIT or interpreter. You could, for example, get a typical set of JIT-related libs using:

Well, we had llvm-config in tools originally and moved it out because it isn't really a tool. Furthermore, it doesn't work 100% yet and probably won't until after 1.7. I can move it if that's where you want it. Reid. On Wed, 2006-04-12 at 23:25 -0500, Chris Lattner wrote: > I recently tried out llvm-config: > > % llvm-config --help > tcsh:

Feedback below.. > <will insert overview blurb here> Big new things: llvm-gcc4, new sparc > backend, Generic vector/SSE/Altivec support, X86 Scalar SSE support, > debugging support, many target-independent codegen improvements, inline asm, > llvm.org/web-reg. > > > Core LLVM IR Improvements: > > * The LLVM IR now has full support for representing

Hello How do I subscribe to samba-docs mailing list? The list is listed at http://samba.kn.vutbr.cz/samba/archives.html however it is not listed on the subscription page at http://lists.samba.org/mailman/ judging by grepping 'samba-docs' in the page and finding nothing. Cl<

I tend to be someone who automatically looks for trends, and the nice thing about having just one list is that it lets me know where people are having problems. Judging by the number of questions we get, one of the biggest challenges for inexperienced rsync users is knowing why a particular file is included or excluded. Way in the back of my mind I see a need for an option that, for every file