search for: floop

Hi LLVM-ers, I'd like to eliminate dead loop with floating point counter using LLVM, but the following loop wasn't optimized by opt. void func() { float i; for (i = 0.0f; i < 1000.0f; i += 1.2f) { } } $ clang -emit-llvm-bc floop.c $ opt -std-compile-opts floop.bc | llvm-dis define void @func(...) nounwind { entry: br label %forinc forinc: ; preds = %forinc, %entry %i.0.reg2mem.0 = phi float [ 0.000000e+00, %entry ], [ %add, %forinc ] ; <float> [#uses=1] %add = add float %i.0.reg2mem.0, 0x3FF3333340000000 ; &l...

...cc" CXX="g++" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" menuselect make[1]: Entering directory `/home/asterisk/rpmbuild/BUILD/asterisk-1.6.1/menuselect' gcc -m64 -march=native -mtune=native -floop-interchange -floop-strip-mine -floop-block -c -o menuselect_stub.o menuselect_stub.c gcc -o menuselect menuselect.o strcompat.o menuselect_stub.o mxml/libmxml.a /usr/bin/ld: i386 architecture of input file `menuselect.o' is incompatible with i386:x86-64 output /usr/bin/ld: i386 architecture...

...asn't optimized by opt. > > void > func() { > float i; > for (i = 0.0f; i < 1000.0f; i += 1.2f) { > } > } FWIW, LLVM optimizer can eliminate this loop if i is incremented by 1.0f Pl. file a bugzilla report. Thanks, - Devang > > > $ clang -emit-llvm-bc floop.c > $ opt -std-compile-opts floop.bc | llvm-dis > > define void @func(...) nounwind { > entry: > br label %forinc > > forinc: ; preds = %forinc, %entry > %i.0.reg2mem.0 = phi float [ 0.000000e+00, %entry ], [ %add, %forinc > ] ; <float> [#uses=1] > %add = ad...

https://bugs.freedesktop.org/show_bug.cgi?id=65310 --- Comment #4 from Emil Velikov <emil.l.velikov at gmail.com> --- Cannot seem to reproduce $ export CFLAGS="-march=native -msse2 -mfpmath=sse -O3 -ffast-math -funroll-loops -fomit-frame-pointer -floop-interchange -floop-strip-mine -floop-block" export CXXFLAGS="$CFLAGS" # Build mesa with Gallium3D hardware drivers $ ./autogen.sh --prefix=/usr --with-dri-drivers= --with-state-trackers=dri --disable-egl --with-gallium-drivers=nouveau --disable-gallium-llvm Note added "--with-...

...> float i; >> for (i = 0.0f; i < 1000.0f; i += 1.2f) { >> } >> } > > FWIW, LLVM optimizer can eliminate this loop if i is incremented by 1.0f > > Pl. file a bugzilla report. > Thanks, > - > Devang >> >> >> $ clang -emit-llvm-bc floop.c >> $ opt -std-compile-opts floop.bc | llvm-dis >> >> define void @func(...) nounwind { >> entry: >> br label %forinc >> >> forinc: ; preds = %forinc, %entry >> %i.0.reg2mem.0 = phi float [ 0.000000e+00, %entry ], [ %add, %...

...39;,t:'0')),k:50.000817634746205,l:'4',n:'0',o:'',s:0,t:'0')),l:'2',n:'0',o:'',t:'0')),version:4 I was thinking that modern compilers are optimizing such cases very aggressively. I quickly checked gcc, there is special option -floop-interchange, but it requires properly configured gcc compiler with Graphite infrastructure enabled. I didn't have that at hand, so I just stopped right there. Loop has no side effects and arrays do not alias, so from my point of view it's safe to do interchange here. I tried different marc...

...; i += 1.2f) { >>> } >>> } >> >> FWIW, LLVM optimizer can eliminate this loop if i is incremented by >> 1.0f >> >> Pl. file a bugzilla report. >> Thanks, >> - >> Devang >>> >>> >>> $ clang -emit-llvm-bc floop.c >>> $ opt -std-compile-opts floop.bc | llvm-dis >>> >>> define void @func(...) nounwind { >>> entry: >>> br label %forinc >>> >>> forinc: ; preds = %forinc, %entry >>> %i.0.reg2mem.0 = phi float [ 0.0...

Hi. I would like to partially apply a function to a list of arguments, and I don't know how to do this in R, without perhaps writing default values to the formals() of my function, or writing to the environment object of a function. For context, my definition of partially apply is: "fix some of the arguments, leaving the others as variables, return a new function that takes the un-fixed

...cts. (for example, floating point control register does not change because the increment does not cause the overflow) Thus I believe the loop as shown above could be removed safely. FYI, gcc -O3 turns fp loop counter into integer, but gcc does not optimize further(eliminate the loop). $ gcc -O3 floop.c _foo: pushl %ebp movl $834, %eax movl %esp, %ebp .align 4,0x90 L2: decl %eax jne L2 -- Syoyo On Fri, Jan 9, 2009 at 1:11 PM, Daniel Berlin <dberlin at dberlin.org> wrote: > FWIW, I believe icc -O3 turns on the equivalent of -ffast-math by default. > I could be misremembering...

FWIW, I believe icc -O3 turns on the equivalent of -ffast-math by default. I could be misremembering which compilers do this though :) This flag allows you to make all kinds of nice simplfiying assumptions about floating point. On Thu, Jan 8, 2009 at 7:45 PM, Owen Anderson <resistor at mac.com> wrote: > I assume it checks that the end condition and the increment can both > be

...S -D__STDC_LIMIT_MACROS -Itools/clang/lib/Frontend/Rewrite -I/sw/src/clang_llvm_dev/clang/lib/Frontend/Rewrite -I/sw/src/clang_llvm_dev/clang/include -Itools/clang/include -Iinclude -I/sw/src/clang_llvm_dev/llvm_trunk/include -fopt-info -pipe -Wall -Wextra -Ofast -DCLS=64 -fPIC -floop-nest-optimize --param simultaneous-prefetches=16 -fprefetch-loop-arrays -msse4.2 -mrecip=all -funroll-loops -fdelete-null-pointer-checks --param prefetch-latency=32 -ffast-math -ftree-vectorize -funsafe-math-optimizations -Wno-error=unused-parameter -Wno-error=type-limits -fPIC...

...Drop support for loading Polly as a plugin 5) Move polly passes and helper libraries such as isl into appropriate directories. E.g., lib/Analysis/Polly, lib/Transforms/Polly and tests into tests/… 6) Introduce a user visible clang flag to enable Polly e.g., -floop-optimize-aggressive 7) Cross-reference Polly documentation and LLVM website 8) Continue testing, fuzzing, and profiling At this point, Polly is available to the wider community, but nobody is affected in the default configuration as long as no explicit options have been chosen. I expect...