search for: ftree

...dragonegg PLUGIN_START_UNIT | dragonegg ac.f90: In function ‘MAIN__’: ac.f90:109:0: internal compiler error: Abort trap Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. This appears to be due to the -ftree-vectorize as -O3 --fno-tree-vectorize doesn't show this ICE but -O2 -ftree-vectorize does. Jack > > Marcus > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc...

On 4/9/2011 6:09 AM, Duncan Sands wrote: > Hi Jack, thanks for the numbers. Any chance of analysing why gcc does better on > those where it does much better than dragonegg? > > Ciao, Duncan. Also, does -fplugin-arg-dragonegg-enable-gcc-optzns get Dragonegg to match GCC performance where GCC was faster? Marcus

Trying to build today's svn on fc5, gcc-4.1.0,amd64: gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I.. -I/usr/include -O2 -fPIC -funswitch-loops -ftree-loop-linear -march=k8 -ftree-vectorize -pipe -mfpmath=sse -frename-registers -O3 -msse -MT nb_celp.lo -MD -MP -MF .deps/nb_celp.Tpo -c nb_celp.c -fPIC -DPIC -o .libs/nb_celp.o nb_celp.c: In function 'nb_encode': nb_celp.c:442: error: 'EncState' has no member named 'frame'...

Hello list, I need/want to build imaptest -- and I can only build it against at least dovecot 1.2 . dovecot 1.2 actually builds just fine but at the end I get the following linker error: /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -O2 -pipe -std=gnu99 -Wall -ftree-dce -ftree-dse -ftree-loop-optimize -ftree-loop-linear -I/usr/lib/gcc/i386-redhat-linux/4.1.1/include -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -Wl,-z -Wl,compreloc -Wl,-z -Wl,norelro -o imap -export...

...o turn on the new GCC auto-vectorization feature within llvmgcc4. Below is the command I used, but nothing was vectorized. Does it mean that llvmgcc4 has disabled this optimization and all I can do is to embed SSE intrinsics in the source code by hand? Thanks! ./llvm-gcc4-x86/bin/llvm-gcc -c -O2 -ftree-vectorize -msse -ftree-vectorizer-verbose=5 -emit-llvm vec.c -o vec.bc ////////////////////vec.c///////////////////////// int a[256], b[256], c[256]; foo () { int i; for (i=0; i<256; i++){ a[i] = b[i] + c[i]; } } -------------- next part -------------- An HTML attachment was scrubbed....

...elow is the command I used, but nothing was >> vectorized. Does it mean that llvmgcc4 has disabled this >> optimization and all I can do is to embed SSE intrinsics in the >> source code by hand? >> >> Thanks! >> >> ./llvm-gcc4-x86/bin/llvm-gcc -c -O2 -ftree-vectorize -msse -ftree- >> vectorizer-verbose=5 -emit-llvm vec.c -o vec.bc >> >> ////////////////////vec.c///////////////////////// >> int a[256], b[256], c[256]; >> foo () { >> int i; >> for (i=0; i<256; i++){ >> a[i] = b[i] + c[i]; >&...

Viswanath Puttagunta wrote: > I responded to your feedback before I started on RFCv3.. and took your > silence as approval :).. I guess that email got lost in your inbox sea > some where.. so re-posting the responses. Sorry, I did see it but I guess I read it rather more quickly than I thought. Apologies for that. > guidance. I wouldn't know where else to put this. Without

...re > within llvmgcc4. Below is the command I used, but nothing was > vectorized. Does it mean that llvmgcc4 has disabled this > optimization and all I can do is to embed SSE intrinsics in the > source code by hand? > > Thanks! > > ./llvm-gcc4-x86/bin/llvm-gcc -c -O2 -ftree-vectorize -msse -ftree- > vectorizer-verbose=5 -emit-llvm vec.c -o vec.bc > > ////////////////////vec.c///////////////////////// > int a[256], b[256], c[256]; > foo () { > int i; > for (i=0; i<256; i++){ > a[i] = b[i] + c[i]; > } > } > > > ______...

...oc-prefer-bytes -fident # -finline-functions-called-once -fivopts -fkeep-static-consts # -fleading-underscore -flocal-alloc -fmove-loop-invariants -fpeephole # -freg-struct-return -fsched-interblock -fsched-spec # -fsched-stalled-insns-dep -fshow-column -fsplit-ivs-in-unroller # -ftoplevel-reorder -ftree-loop-im -ftree-loop-ivcanon # -ftree-loop-optimize -ftree-vect-loop-version -funit-at-a-time # -fverbose-asm -fzero-initialized-in-bss -m128bit-long-double -m32 -m80387 # -maccumulate-outgoing-args -malign-stringops -matt-stubs # -mconstant-cfstrings -mfancy-math-387 -mfp-ret-in-387 -mieee-fp -mmmx...

...profile feedback data files. See -fprofile-dir. -fprofile-use-fprofile-use=pathEnable profile feedback-directed optimizations, and the following optimizations which are generally profitable only with profile feedback available: -fbranch-probabilities, -fvpt, -funroll-loops, -fpeel-loops, -ftracer, -ftree-vectorize, and ftree-loop-distribute-patterns. By default, GCC emits an error message if the feedback profiles do not match the source code. This error can be turned into a warning by using -Wcoverage-mismatch. Note this may result in poorly optimized code. If path is specified, GCC looks at the...

...fied by multiplying the induction range by N and reducing the number of load/sub/store lanes to one, in which case, loop vectorization becomes trivial. Do you know if the GCC SLP Vectorizer vectorizes this, or is it their Loop > Vectorizer ? > Good question. What vectorizer does the "-ftree-vectorizer" turns on? Because if I use "-fno-tree-vectorize", the code remains scalar. cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131014/2b7f646a/attachment.html>

...but nothing was >>> vectorized. Does it mean that llvmgcc4 has disabled this >>> optimization and all I can do is to embed SSE intrinsics in the >>> source code by hand? >>> >>> Thanks! >>> >>> ./llvm-gcc4-x86/bin/llvm-gcc -c -O2 -ftree-vectorize -msse -ftree- >>> vectorizer-verbose=5 -emit-llvm vec.c -o vec.bc >>> >>> ////////////////////vec.c///////////////////////// >>> int a[256], b[256], c[256]; >>> foo () { >>> int i; >>> for (i=0; i<256; i++){ >>&g...

...on support in the near term, it seems that FSF gcc/dragonegg is the best approach to hunt for vectorization issues in llvm. Might we be able to split the difference here and create a variant of -fplugin-arg-dragonegg-enable-gcc-optzns which only enables a limited set of FSF gcc optimizations (like -ftree-vectorize) required to enable FSF gcc's autovectorization under dragonegg? For instance couldn't dragonegg just honor -ftree-vectorize when it or -O3 are passed as compiler flags? Jack > > I have some sympathy for both viewpoints... > > Ciao, Duncan.

trying to install this new release and got this message. I tried to locate the dev. pkgs but no luck. yum install did not bring back anything. also tried to search on Fedora to loacate them to install but no luck. any help would be appreciated. Larry checking for X... no configure: error: X development files not found. Wine will be built without X support, which probably isn't what you want.

...o make an unoptimized build for some reason > (e.g., testing or debugging), you've broken that. Thanks. After re-referring to the NEON Programmer's guide carefully http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0018a/index.html the appropriate flag should have been "-ftree-vectorize". I can also confirm that -O2 and -O3 produces almost same output. What I was comparing when I meant "painful" is when I don't use any optimization level.. which I tried during unit testing. But it looks like for opus, the default optimization flag is -O2... so just ad...

This is almost ideal for SLP vectorization, except for two problems: 1. We have 4 stores to consecutive locations, but the last element is the constant zero, and not an additional SUB. At the moment we don’t have support for idempotence operations, but this is something that we should add. 2. The values that we are subtracting come from 3 loads. We usually load 4 elements from memory, or

...the error produce by ./configure CFLAGS='-O3 -faltivec -fgcse- sm -funroll-loops -fstrict-aliasing -fsched-interblock -falign- loops=16 -falign-jumps=16 -falign-functions=16 -malign-natural - freorder-blocks -freorder-blocks-and-partition -mpowerpc-gfxopt - mpowerpc-gpopt -fstrict-aliasing -ftree-vectorize -mtune=G5 -mcpu=G5' FFLAGS='-O3 -faltivec -fgcse-sm -funroll-loops -fstrict-aliasing - fsched-interblock -falign-loops=16 -falign-jumps=16 -falign- functions=16 -malign-natural -freorder-blocks -freorder-blocks-and- partition -mpowerpc-gfxopt -mpowerpc-gpopt -fstrict-aliasing...

...are other release stopping bugs/issues that you think should be fixed before the final 3.2 release but are not listed below then please add them to the Bug 13893 - "Umbrella bug for 3.2 release". As of today Tuesday Nov 27th following release blocking bugs are still open: 12664 - O2 -ftree-vectorize -fplugin-arg-dragonegg-enable-gcc-optzns on mdbx.f90 confuses dragoneg 13561 - LLVM ERROR: Cannot select: 0x14214bb10: i16 = extract_vector_elt 0x14214b910, 0x142142c10 14116 - Inliner incorrectly combines cleanup and catch landing pads 14279 - mishandling of implicit move in class wi...

...he results, which in hindsight I now realise I should have! (Never mind!) However, I have got the following results building with GCC 4.5.1: gcc -O3 Works fine gcc -march=barcelona Works fine gcc -O2 -march=barcelona -fgcse-after-reload -finline-functions -fipa_cp_clone -fpredictive-commoning -ftree-pre-partial-partial -ftree-vectorize -funswitch-loops Works fine gcc -O3 -march=barcelona explorer crashes out (three times?) rundll32 crashes out winecfg loads gcc -O3 -march=barcelona basically breaks something badly. I'm not sure if Wine should support -march or what the policy is, or if...

Not sure if it is just my configuration but building the RPM on Centos x86_64 fails. Also not sure if this is to be fixed in the Makefile or in the configure. The rpm compile proceeds apace until the build reaches the %files section. Here it uses the _libdir directive to look for the libraries that have just been compiled. However in an x86_64 environment the _libdir directive points to lib64