search for: llvm_oqfmvn

...oo.bc -o foo.s clang-cc bar.c -o /tmp/llvm_1zAqik/bar.bc llvm-ld /tmp/llvm_1zAqik/bar.bc -o /tmp/llvm_1zAqik/bar.bc llc -f /tmp/llvm_1zAqik/bar.bc -o bar.s > ** Use of -g causes llvm-ld to run with -disable-opt > $ mcc16 -S -g foo.c $ mcc16 -dry-run -S -g foo.c clang-cc foo.c -o /tmp/llvm_oQFmVn/foo.bc llvm-ld -disable-opt /tmp/llvm_oQFmVn/foo.bc -o /tmp/llvm_oQFmVn/foo.bc llc -f /tmp/llvm_oQFmVn/foo.bc -o foo.s > ** -I is passed to clang-cc, -pre-RA-sched=list-burr to llc. > $ mcc16 -S -g -I ../include -pre-RA-sched=list-burr foo.c $ mcc16 -dry-run -S -g -I ../include -pre-RA-s...

> 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

.../tmp/llvm_1zAqik/bar.bc > llvm-ld /tmp/llvm_1zAqik/bar.bc -o /tmp/llvm_1zAqik/bar.bc > llc -f /tmp/llvm_1zAqik/bar.bc -o bar.s > > > ** Use of -g causes llvm-ld to run with -disable-opt > > $ mcc16 -S -g foo.c > > $ mcc16 -dry-run -S -g foo.c > clang-cc foo.c -o /tmp/llvm_oQFmVn/foo.bc > llvm-ld -disable-opt /tmp/llvm_oQFmVn/foo.bc -o /tmp/llvm_oQFmVn/foo.bc > llc -f /tmp/llvm_oQFmVn/foo.bc -o foo.s > > > ** -I is passed to clang-cc, -pre-RA-sched=list-burr to llc. > > $ mcc16 -S -g -I ../include -pre-RA-sched=list-burr foo.c > > $ mcc16 -dry-run...