Displaying 3 results from an estimated 3 matches for "llvm_6ibgr9".
2009 Jun 07
0
[LLVMdev] llvmc for PIC16
...illustrating the features you requested:
> 2. If the user has specified to generate the final executable, then
> llvm-ld should run on all the .bc files generated by clang and create a
> single optimized .bc file for further tools.
$ mcc16 -dry-run foo.c bar.c
clang-cc foo.c -o /tmp/llvm_6ibgr9/foo.bc
clang-cc bar.c -o /tmp/llvm_6ibgr9/bar.bc
llvm-ld /tmp/llvm_6ibgr9/foo.bc /tmp/llvm_6ibgr9/bar.bc \
-o /tmp/llvm_6ibgr9/tmp.bc
llc -f /tmp/llvm_6ibgr9/tmp.bc -o /tmp/llvm_6ibgr9/tmp.s
native-as /tmp/llvm_6ibgr9/tmp.s -o /tmp/llvm_6ibgr9/tmp.o
native-ld /tmp/llvm_6ibgr9/tmp.o -o a.ou...
2009 Jun 05
4
[LLVMdev] llvmc for PIC16
> I'll be happy to answer any further questions you may have, feel free to e-mail
> me directly (though right now our mail server is down)
>
The salient features that we want to have in the driver are:
1. llvm-ld will be used as "The Optimizer".
2. If the user has specified to generate the final executable, then
llvm-ld should run on all the .bc files generated by clang
2009 Jun 15
3
[LLVMdev] llvmc for PIC16
...requested:
>
> > 2. If the user has specified to generate the final executable, then
> > llvm-ld should run on all the .bc files generated by clang and create a
> > single optimized .bc file for further tools.
>
> $ mcc16 -dry-run foo.c bar.c
> clang-cc foo.c -o /tmp/llvm_6ibgr9/foo.bc
> clang-cc bar.c -o /tmp/llvm_6ibgr9/bar.bc
> llvm-ld /tmp/llvm_6ibgr9/foo.bc /tmp/llvm_6ibgr9/bar.bc \
> -o /tmp/llvm_6ibgr9/tmp.bc
> llc -f /tmp/llvm_6ibgr9/tmp.bc -o /tmp/llvm_6ibgr9/tmp.s
> native-as /tmp/llvm_6ibgr9/tmp.s -o /tmp/llvm_6ibgr9/tmp.o
> native-ld /tmp/...