search for: wllc

Hi all, In the good old llvmc, the -Wo flag could be used to pass arguments to the optimizer. Is there a similar mechanism anywhere for clang? Is there also a similar mechanism to -Wllc? Thanks! Harel Cain -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120304/0e5c7267/attachment.html>

...tion of llvmc and wasn't given much thought. > I don't see an easy way to disable or override this option when invoking > llvmc on the command line. I removed the '-relocation-model' bit from the default invocation string for llc. To pass arguments to llc, use the new "-Wllc" option. -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

> In the good old llvmc, the -Wo flag could be used to pass arguments to the > optimizer. Is there a similar mechanism anywhere for clang? Is there also a > similar mechanism to -Wllc? -mlvm will handle all of them -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

According to the FAQ llvmc is considered experimental/unsupported. But FWIW, here's an issue I found while trying to use it on 32 bit x86 systems. tools/llvmc/plugins/Base/Base.td hardcodes the -relocation-model=pic option into invocations of llc: def llc : Tool< [(in_language "llvm-bitcode"), (out_language "assembler"), (output_suffix "s"), (cmd_line

...un, Mar 4, 2012 at 15:03, Anton Korobeynikov <anton at korobeynikov.info>wrote: > > In the good old llvmc, the -Wo flag could be used to pass arguments to > the > > optimizer. Is there a similar mechanism anywhere for clang? Is there > also a > > similar mechanism to -Wllc? > -mlvm will handle all of them > > -- > With best regards, Anton Korobeynikov > Faculty of Mathematics and Mechanics, Saint Petersburg State University > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/...

...x for push and pop. Is there any ways to resolve or overcome that? I need to keep the assembly inline, and not move it to the .s files. I used the following llvmc: llvm version 2.9 Optimized build. Built Sep 8 2011 (11:43:28). Host: i386-pc-linux-gnu Host CPU: core2 Using the following flags:-Wllc,="-mtriple=arm-linux-eabi" -fmessage-length=0 -std=c99 -Wno-trigraphs -O3 -fpic -Wreturn-type -Wunused-variable -fvisibility=hidden -D__ARM_EABI__ -DANDROID -isysroot/usr/local/android/android-ndk-r6b/platforms/android-8/arch-arm Thanks a lot,Moshe -------------- next part -...

...o /tmp/llvm_6ibgr9/tmp.o native-ld /tmp/llvm_6ibgr9/tmp.o -o a.out > 3. -Wo <options> - pass optimizations to the llvm-ld > 4. mcc16 -Wl <options> - pass options to native linker. > 5. mcc16 -Wa <options> - pass options to native assembler. $ mcc16 -dry-run -Wo,-opt1 -Wllc,-opt2 -Wa,-opt3 -Wl,-opt4 foo.c clang-cc foo.c -o /tmp/llvm_92HLCj/foo.bc llvm-ld -opt1 /tmp/llvm_92HLCj/foo.bc -o /tmp/llvm_92HLCj/tmp.bc llc -opt2 -f /tmp/llvm_92HLCj/tmp.bc -o /tmp/llvm_92HLCj/tmp.s native-as -opt3 /tmp/llvm_92HLCj/tmp.s -o /tmp/llvm_92HLCj/tmp.o native-ld -opt4 /tmp/llvm_92...

> 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

Mikhail Glushenkov wrote: > I removed the '-relocation-model' bit from the default invocation > string for llc. To pass arguments to llc, use the new "-Wllc" > option. I'd say that this is the proper solution, even though it breaks backward compatibility on x86_64. But given that llvmc is still considered experimental, better do it now than later. ;-) Thanks a lot for creating llvmc, it's very useful! -- Dr. Albert Gr"af Dept....

...me that? I need to keep the assembly inline, and not move it to the .s files. > > I used the following llvmc: > llvm version 2.9 > Optimized build. > Built Sep 8 2011 (11:43:28). > Host: i386-pc-linux-gnu > Host CPU: core2 > > Using the following flags: > -Wllc,="-mtriple=arm-linux-eabi" -fmessage-length=0 -std=c99 -Wno-trigraphs -O3 -fpic -Wreturn-type -Wunused-variable -fvisibility=hidden -D__ARM_EABI__ -DANDROID -isysroot/usr/local/android/android-ndk-r6b/platforms/android-8/arch-arm > > Thanks a lot, > Moshe > ________________...

...ative-ld /tmp/llvm_6ibgr9/tmp.o -o a.out > > > 3. -Wo <options> - pass optimizations to the llvm-ld > > 4. mcc16 -Wl <options> - pass options to native linker. > > 5. mcc16 -Wa <options> - pass options to native assembler. > > $ mcc16 -dry-run -Wo,-opt1 -Wllc,-opt2 -Wa,-opt3 -Wl,-opt4 foo.c > clang-cc foo.c -o /tmp/llvm_92HLCj/foo.bc > llvm-ld -opt1 /tmp/llvm_92HLCj/foo.bc -o /tmp/llvm_92HLCj/tmp.bc > llc -opt2 -f /tmp/llvm_92HLCj/tmp.bc -o /tmp/llvm_92HLCj/tmp.s > native-as -opt3 /tmp/llvm_92HLCj/tmp.s -o /tmp/llvm_92HLCj/tmp.o > native-...