search for: fpstack

...M Backend is using xmms it involves a lot of register moves. llc has one option -mcpu=686, where output does not use xmm but it disables some other instructions also. Is there any fine grain optimization flag like ( -mfpmath = 387 which is present in gcc) which would just instruction backend to use fpstack instead of SSE instructions and still not limit the instructions Thanks --Kapil . -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100607/2ae7d924/attachment.html>

...9; report (TEST.jit.Makefile and TEST.jit.report) are a simple example to demonstrate this. For example, go into llvm-test/MultiSource/Benchmarks/Olden and run: $ make TEST=jit report This should spit out something like this (on X86): Name: | Total CodeGen InstSel LiveVar RA FPStack Peep | MCSize #MCInsts #Glob | #store #load #fp #fxch | treeadd/treeadd | 6.38 0.0300 0.0133 0.0023 0.0054 0.0001 0.0002 | 1000 245 115 | * 10 * * | power/power | 4.87 0.0899 0.0368 0.0044 0.0366 0.0022 0.0003 | 5720 1336 702 | 105 216 790...

Hello , I am compiling SPEC 2000 benchmarks with llvm .Got stuck with calculating "execution time" of all the .bc and native files. The log for nightly test itself gives execution times but I am passing the bytecode files to my pass which gives another bytecode file.I have to calculate execution time of such bytecode and native files as well.If i simply do this: time lli

...es. The 'jit' report (TEST.jit.Makefile and TEST.jit.report) are a simple example to demonstrate this. For example, go into llvm-test/MultiSource/Benchmarks/Olden and run: $ make TEST=jit report This should spit out something like this (on X86): Name: | Total CodeGen InstSel LiveVar RA FPStack Peep | MCSize #MCInsts #Glob | #store #load #fp #fxch | treeadd/treeadd | 6.38 0.0300 0.0133 0.0023 0.0054 0.0001 0.0002 | 1000 245 115 | * 10 * * | power/power | 4.87 0.0899 0.0368 0.0044 0.0366 0.0022 0.0003 | 5720 1336 702 | 105 216 790 58 | tsp/tsp | 4.72 0.1400 0.0439 0.0073 0.0591 0.0023 0.00...

...Mflops: 127.22 -O3 -msse3 Ok, thanks Jon! I diff'd the files and the -msse2 and -msse3 code is identical, so we're not doing anything wrong with -msse3 :). OTOH, the perf drop from sse -> sse2 is concerning. The difference here is that we do double math in SSE regs instead of FPStack regs. In this case, using the fp stack avoids some cross-class register copying. We could improve the code generator to notice and handle this, I added this note to the x86 backend with some details: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090202/073254.html This is a...

Some wheird problem, Target/X86 builds okay now. But there seems to be another problem with the Cygwin build :- make[4]: Entering directory `/usr/build/llvm/lib/Target/SparcV9/ModuloScheduling' llvm[4]: Compiling ModuloSchedulingSuperBlock.cpp for Debug build /usr/src/llvm/lib/Target/SparcV9/ModuloScheduling/ModuloSchedulingSuperBlock.cpp : In member function `virtual bool