public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc at crg4 dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/61929] New: Graphite: Banerjee and Omega differ on distance vectors (internal compiler error in compute_affine_dependence) Date: Sun, 27 Jul 2014 19:39:00 -0000 [thread overview] Message-ID: <bug-61929-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61929 Bug ID: 61929 Summary: Graphite: Banerjee and Omega differ on distance vectors (internal compiler error in compute_affine_dependence) Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: gcc at crg4 dot com -fcheck-data-deps finds a discrepancy between Banerjee and Omega in gcc 4.9 when compiling the latest RIES source. The error message is: (Number of distance vectors differ: Banerjee has 1, Omega has 2. Banerjee dist vectors: 0 Omega dist vectors: 0 1 data dependence relation: (Data Dep: #(Data Ref: # bb: 44 # stmt: debug_L.555_92 = debug_L; # ref: debug_L # base_object: MEM[(short int *)&debug_L]; #) #(Data Ref: # bb: 44 # stmt: debug_L = debug_L.568_93; # ref: debug_L # base_object: MEM[(short int *)&debug_L]; #) inner loop index: 0 loop nest: (1 ) distance_vector: 0 distance_vector: 1 direction_vector: = direction_vector: + ) ) ries.c: In function ‘set_debug_opts’: ries.c:10391:6: internal compiler error: in compute_affine_dependence, at tree-data-ref.c:4233 void set_debug_opts(char * str) ^ Please submit a full bug report, with preprocessed source if appropriate. ---- The RIES source is available at http://www.mrob.com/pub/ries/src/ries.c.txt and is self-contained (no .h files etc.). I can cause the error with gcc -o ries ries.c -lm -O1 -fcheck-data-deps but not gcc -o ries ries.c -lm -O0 -fcheck-data-deps however I cannot narrow this down to a particular optimization causing the difficulty since gcc -o ries ries.c -lm -O1 -fcheck-data-deps -fno-branch-count-reg -fno-combine-stack-adjustments -fno-compare-elim -fno-cprop-registers -fno-defer-pop -fno-forward-propagate -fno-guess-branch-probability -fno-if-conversion -fno-if-conversion2 -fno-inline-functions-called-once -fno-ipa-profile -fno-ipa-pure-const -fno-ipa-reference -fno-merge-constants -fno-move-loop-invariants -fno-shrink-wrap -fno-split-wide-types -fno-tree-bit-ccp -fno-tree-ccp -fno-tree-ch -fno-tree-copy-prop -fno-tree-copyrename -fno-tree-dce -fno-tree-dominator-opts -fno-tree-dse -fno-tree-fre -fno-tree-pta -fno-tree-sink -fno-tree-slsr -fno-tree-sra -fno-tree-ter still causes the error. It appears that at least one of the Omega and Banerjee algorithms are incorrect. I am running > gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.9.1-1ubuntu2~14.04.3' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --disable-vtable-verify --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.9.1 (Ubuntu 4.9.1-1ubuntu2~14.04.3) > uname -a Linux zed 3.2.0-56-generic #86-Ubuntu SMP Wed Oct 23 09:20:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I have no knowledge of either Graphite or RIES; I am merely reporting what appears to be a bug (indeed, as instructed by gcc itself). >From gcc-bugs-return-457190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 27 19:39:37 2014 Return-Path: <gcc-bugs-return-457190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 24533 invoked by alias); 27 Jul 2014 19:39:36 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 23921 invoked by uid 48); 27 Jul 2014 19:39:29 -0000 From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/61928] a fortran90 program compiles on hopper at NERSC but not under gfortran 4.9.0 Date: Sun, 27 Jul 2014 19:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: version Message-ID: <bug-61928-4-R3stjDV3gb@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-61928-4@http.gcc.gnu.org/bugzilla/> References: <bug-61928-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-07/txt/msg01781.txt.bz2 Content-length: 407 https://gcc.gnu.org/bugzilla/show_bug.cgi?ida928 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unknown |4.9.0 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- You are not linking with the linpack library.
next reply other threads:[~2014-07-27 19:39 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-27 19:39 gcc at crg4 dot com [this message] 2014-07-29 3:24 ` [Bug tree-optimization/61929] " gcc at crg4 dot com 2014-07-29 4:10 ` gcc at crg4 dot com 2014-07-29 4:56 ` gcc at crg4 dot com 2014-07-29 15:10 ` gcc at crg4 dot com 2015-06-22 13:11 ` [Bug tree-optimization/61929] [Graphite]: " gcc at crg4 dot com 2015-06-22 13:50 ` gcc at crg4 dot com 2015-06-22 14:30 ` gcc at crg4 dot com 2015-06-22 14:32 ` gcc at crg4 dot com 2015-07-16 16:37 ` spop at gcc dot gnu.org 2015-07-17 16:34 ` spop at gcc dot gnu.org 2015-07-17 16:35 ` spop at gcc dot gnu.org 2015-07-18 0:47 ` spop at gcc dot gnu.org 2015-07-23 21:10 ` nheghathivhistha at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-61929-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).