search for: 200000l

...- Avoid sign extensions by replacing all 32-bit ints with longs, as Polly seems to model using 64-bit loop counters - Avoid interrupting control flow through -ffast-math and moving mallocs to the top of the code So to compile, we have: clang -I. -O3 -g3 -Wall -Wextra -std=c99 -D_POSIX_C_SOURCE=200000L -ffast-math -mllvm -polly -mllvm -polly-dot -mllvm -polly-process-unprofitable -mllvm -polly-vectorizer=stripmine -mllvm -polly-dependences-computeout=0 -c -o localcolorcorrection.o localcolorcorrection.c Unfortunately, LLVM 5.0.1 generates different results in analyzing the CFG compared to LLVM 3...

...with longs, as >> Polly seems to model using 64-bit loop counters >> - Avoid interrupting control flow through -ffast-math and moving mallocs >> to the top of the code >> >> So to compile, we have: >> clang -I. -O3 -g3 -Wall -Wextra -std=c99 -D_POSIX_C_SOURCE=200000L >> -ffast-math -mllvm -polly -mllvm -polly-dot -mllvm >> -polly-process-unprofitable -mllvm -polly-vectorizer=stripmine -mllvm >> -polly-dependences-computeout=0 -c -o localcolorcorrection.o >> localcolorcorrection.c >> >> Unfortunately, LLVM 5.0.1 generates diff...

When I use the -v I can modify the size of the heap, as assessed by gc(), but the -n key seems to be without effect ? On a machine with 48 mB ram I can load the libraries without problem, but on my own 36 mB ram machine, I get dynload problems with the larger, eg survival4. Any suggestions ? Troels -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list

When I use the -v I can modify the size of the heap, as assessed by gc(), but the -n key seems to be without effect ? On a machine with 48 mB ram I can load the libraries without problem, but on my own 36 mB ram machine, I get dynload problems with the larger, eg survival4. Any suggestions ? Troels -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list