search for: udis86

Debug build on x86_64 with`--with-udis86=<path>' option to 'configure' seems broken. Configure command line: ./configure --disable-optimized --enable-assertions --enable-debug-runtime --enable-debug-symbols --enable-jit --enable-pic --enable-targets=x86_64 --with-udis86=/somepath/udis86/udis86-1.7 At least 2 issues: (...

To disassemble jit code I typically use the udis86 support. Are there patches floating around to support SSE4.1 and SSE4.2 in this? I'd like to use it on a nehalem based machine and investigate the llvm code generation for SSE4.2 in a jit context. thanks bill -------------- next part -------------- An HTML attachment was scrubbed... URL: <h...

...--program-prefix=llvm- Thread model: posix llvm config.status: It was created by llvm configure 2.8svn, which was generated by GNU Autoconf 2.60. Invocation command line was $ ./configure --prefix=/home/zoewolk/RESEARCH/LLVMSystem --enable-optimized --enable-jit --enable-targets=x86,cpp --with-udis86=/home/zoewolk/RESEARCH/udis86/lib --with-llvmgccdir=/home/zoewolk/RESEARCH/LLVMSystem Linux karmic kernel 2.6.27.5 x86_64 SMP gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build) On Tue, Jun 29, 2010 at 6:58 PM, Zoe Wolk <zoewolk at gmail.com> wrote: > Hi Nicolas, > No, I...

Hi Nicolas, No, I built llvm-gcc myself by checking it out via svn, using these instructions: http://llvm.org/docs/GCCFEBuildInstrs.html thanks -Z > Hi Zoe > (Please, try to reply to the same thread) > I think you may have an old version of llvm-gcc. Did you compile > llvm-gcc yourself? The provided llvm-gcc binary for llvm 2.7 is > too old for vmkit. > > Nicolas >

...osix > > llvm config.status: > It was created by llvm configure 2.8svn, which was > generated by GNU Autoconf 2.60. Invocation command line was > > $ ./configure --prefix=/home/zoewolk/RESEARCH/LLVMSystem > --enable-optimized --enable-jit --enable-targets=x86,cpp > --with-udis86=/home/zoewolk/RESEARCH/udis86/lib > --with-llvmgccdir=/home/zoewolk/RESEARCH/LLVMSystem > > Linux karmic kernel 2.6.27.5 x86_64 SMP > gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build) > > > > On Tue, Jun 29, 2010 at 6:58 PM, Zoe Wolk <zoewolk at gmail.com&gt...

...ig.status: >> It was created by llvm configure 2.8svn, which was >> generated by GNU Autoconf 2.60. Invocation command line was >> >> $ ./configure --prefix=/home/zoewolk/RESEARCH/LLVMSystem >> --enable-optimized --enable-jit --enable-targets=x86,cpp >> --with-udis86=/home/zoewolk/RESEARCH/udis86/lib >> --with-llvmgccdir=/home/zoewolk/RESEARCH/LLVMSystem >> >> Linux karmic kernel 2.6.27.5 x86_64 SMP >> gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build) >> >> >> >> On Tue, Jun 29, 2010 at 6:58 PM, Zoe...

...lvm built from svn on 64 bit x86 architecture). I had two questions that would help me get kickstarted over the holidays. Is there any easy way to get the jit to dump the assembly equivalent of the generated machine code? In the documentation so far I've not seen it - though I've built it udis86 support turned on. Is there a small but runnable example of generating vector code that is then jitted to packed SSE code? TIA! /B

...ig.status: >> It was created by llvm configure 2.8svn, which was >> generated by GNU Autoconf 2.60. Invocation command line was >> >> $ ./configure --prefix=/home/zoewolk/RESEARCH/LLVMSystem >> --enable-optimized --enable-jit --enable-targets=x86,cpp >> --with-udis86=/home/zoewolk/RESEARCH/udis86/lib >> --with-llvmgccdir=/home/zoewolk/RESEARCH/LLVMSystem >> >> Linux karmic kernel 2.6.27.5 x86_64 SMP >> gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build) >> >> >> >> On Tue, Jun 29, 2010 at 6:58 PM, Zoe...

...t's not actually showing what the JIT is >> generating. How can I dump the JIT generated code, as native >> assembler? It's a debugging requirement only. > > I think there is disassembly capability built-in. See JITEmitter.cpp That's only for x86, and only if you have udis86. I was using (indirectly) an AsmEmitter that is added by TargetMachine::addPassesToEmitFile, and now that I have a better understanding of what's going on, I realise there isn't really any facility to do what I need. Antony Blakey ------------- CTO, Linkuistics Pty Ltd Ph: 0438 840...

Thanks Nicolas for your help with my build problems with vmkit. Yes, I was missing ant -- great catch (I'm on a newly installed machine). That fix with this configuration, gets me to the error below. Any thoughts (build tools, other I may be missing that are not checked for)? Are there steps that you suggest I try to gather more information on the problem? Also -- it seems to be building

...It was created by llvm configure 2.8svn, which was >>> generated by GNU Autoconf 2.60. Invocation command line was >>> >>> $ ./configure --prefix=/home/zoewolk/RESEARCH/LLVMSystem >>> --enable-optimized --enable-jit --enable-targets=x86,cpp >>> --with-udis86=/home/zoewolk/RESEARCH/udis86/lib >>> --with-llvmgccdir=/home/zoewolk/RESEARCH/LLVMSystem >>> >>> Linux karmic kernel 2.6.27.5 x86_64 SMP >>> gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build) >>> >>> >>> >>> On Tu...

...#39;re unable to build some projects that rely on LLVM CMake modules being installed. It also has semi-random shared library naming which means that most of the external software doesn't support linking to it, and instead links to the static libraries. CMake on the other hand lacks support for udis86 code and OCaml bindings, with the latter explicitly requested by our users. I recall it also having unexpected test failures but that may have changed since I last tried it. While it supports building llvm & clang separately, it still pokes llvm build dirs (even if they don't exist anymore)...

Antony, > That's only for x86, and only if you have udis86. I was using > (indirectly) an AsmEmitter that is added by > TargetMachine::addPassesToEmitFile, and now that I have a better > understanding of what's going on, I realise there isn't really any > facility to do what I need. There is special command line switch in lli ca...

Hi, I'm experimenting with using LLVM to generate dynamic FFI bridges in VisualWorks Smalltalk. LLVM is an amazing thing! I'm going from dynamically generated assembler source to machine code, and I have that all working, copied from the llc tool and the JIT example. I have two questions: 1. What optimization passes, if any, should I run on the module before I pass it to the

On Nov 7, 2007, at 6:10 PM, Antony Blakey wrote: > Hi, > I'm experimenting with using LLVM to generate dynamic FFI bridges > in VisualWorks Smalltalk. LLVM is an amazing thing! I'm going from > dynamically generated assembler source to machine code, and I have > that all working, copied from the llc tool and the JIT example. I > have two questions: > > 1. What