Displaying 9 results from an estimated 9 matches for "llvm33".
Did you mean:
llvm32
2013 Mar 20
2
[LLVMdev] error: unable to get target for 'armv5', see --version and --triple.
Current llvm svn fails make check when built for only x86...
[100%] Running the LLVM regression tests
FAIL: LLVM :: DebugInfo/inlined-vars.ll (3994 of 7466)
******************** TEST 'LLVM :: DebugInfo/inlined-vars.ll' FAILED ********************
Script:
--
/sw/src/fink.build/llvm33-3.3-0/llvm-3.3/build/bin/./llc -O0 < /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/test/DebugInfo/inlined-vars.ll | /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/build/bin/./FileCheck /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/test/DebugInfo/inlined-vars.ll -check-prefix ARGUMENT
/sw/src/fink.build/llvm33-3...
2013 Mar 20
0
[LLVMdev] error: unable to get target for 'armv5', see --version and --triple.
...hines that are armv5 native catch this)
>
> [100%] Running the LLVM regression tests
> FAIL: LLVM :: DebugInfo/inlined-vars.ll (3994 of 7466)
> ******************** TEST 'LLVM :: DebugInfo/inlined-vars.ll' FAILED ********************
> Script:
> --
> /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/build/bin/./llc -O0 < /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/test/DebugInfo/inlined-vars.ll | /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/build/bin/./FileCheck /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/test/DebugInfo/inlined-vars.ll -check-prefix ARGUMENT
> /sw/src/fink.build/llv...
2013 Mar 20
1
[LLVMdev] error: unable to get target for 'armv5', see --version and --triple.
...h this)
>
>>
>> [100%] Running the LLVM regression tests
>> FAIL: LLVM :: DebugInfo/inlined-vars.ll (3994 of 7466)
>> ******************** TEST 'LLVM :: DebugInfo/inlined-vars.ll' FAILED ********************
>> Script:
>> --
>> /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/build/bin/./llc -O0 < /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/test/DebugInfo/inlined-vars.ll | /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/build/bin/./FileCheck /sw/src/fink.build/llvm33-3.3-0/llvm-3.3/test/DebugInfo/inlined-vars.ll -check-prefix ARGUMENT
>> /sw/src/fink.build...
2013 Nov 23
0
[LLVMdev] pb05 benchmarks for llvm 3.3/3.4svn
...we may be leaving some potential vectorization improvements on the table here.
Jack
Tested on x86_apple-darwin12
Compile Flags: -fplugin=/sw/lib/gcc4.8/lib/dragonegg.so -specs=/sw/lib/gcc4.8/lib/integrated-as.specs -ffast-math -funroll-loops -O3
Run time (secs)
Benchmark llvm33-stock-de llvm34-stock-de llvm33-de-optnz llvm34-de-optnz
ac 11.57 11.29 8.14 8.07
aermod 16.46 16.79 14.43 14.59
air 6.79 7.22 5.29...
2014 Sep 09
2
[LLVMdev] VMKit is retired (but you can help if you want!)
...incorrect) edit to `static-gc-printer.so` described in an earlier post: http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-August/076128.html :
cd /path/to/vmkit/tools/trainer
javac HelloWorld.java
../../Debug+Asserts/bin/vmjc -main=HelloWorld -print-aot-stats HelloWorld.class
/path/to/llvm33/bin/llc -load=../../Debug+Asserts/lib/static-gc-printer.so HelloWorld.class.bc
That produces for me a reasonable native assembly file.
Next I assemble and link, using a set of libraries/objects inspired by `llcj` and refined by a semi-automated trial-and-error:
/path/to/llvm33/bin/clang++...
2014 Sep 09
2
[LLVMdev] VMKit is retired (but you can help if you want!)
...gure differently.
> >
> > I start with a clean checkout of the VMKit repository into
> /path/to/vmkit_test-clean . I'm on x86_64 using OpenJDK1.6 as follows:
> >
> > ==========
> > /path/to/vmkit_test-clean
> > ./configure --with-llvm-config-path=/path/to/llvm33/bin/llvm-config
> --with-classpath-impl=openjdk
> --with-openjdk-path=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64
> > ==========
> >
> > I have PATH set to provide `javac` as
> /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/bin/javac and
> LD_LIBRARY_PATH to include...
2014 Oct 28
2
[LLVMdev] DragonEgg3.3 support for gcc cross compilers
.../path/to/gcc464/bin/gcc -fplugin=/path/to/dragonegg.so
> -fplugin-arg-dragonegg-emit-ir -S -o hello.ll hello.c
> I also chose to specify the full path of dragonegg.so, so I didn't have to
> be concerned with library paths.
>
> Then you should be able to manually use your backend (llvm33/bin/llc,
> assembler, etc.) to generate an architecture-specific object. Once you've
> got all those components, you should be able to get everything integrated
> with just one gcc compiler-driver invocation.
>
> HTH,
> Brian
>
>
>
>
> On Oct 27, 2014, at 11:53...
2014 Oct 28
3
[LLVMdev] DragonEgg3.3 support for gcc cross compilers
...g.so
> >> -fplugin-arg-dragonegg-emit-ir -S -o hello.ll hello.c
> >> I also chose to specify the full path of dragonegg.so, so I didn't have
> to
> >> be concerned with library paths.
> >>
> >> Then you should be able to manually use your backend (llvm33/bin/llc,
> >> assembler, etc.) to generate an architecture-specific object. Once
> you've
> >> got all those components, you should be able to get everything
> integrated
> >> with just one gcc compiler-driver invocation.
> >>
> >> HTH,
> &...
2014 Oct 28
2
[LLVMdev] DragonEgg3.3 support for gcc cross compilers
I am using a gcc (v 4.8.2) cross compiler for the tilera architecture.
There is an LLVM (v 3.3) cross compiler available for tilera (
http://tilera.github.io/llvm),
but the frontend only has partial support for certain tilera intrinsics and
no OpenMP support.
Hence, I have decided to use DragonEgg (v 3.3) to resolve this. I was able
to build
DragonEgg, but when I pass the command line argument