public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/50913] [4.7 Regression] ICE in scan_tree_for_params_right_scev, at graphite-sese-to-poly.c:633 compiling libgfortran with -floop-interchange -m32 Date: Mon, 07 Nov 2011 13:08:00 -0000 [thread overview] Message-ID: <bug-50913-4-QzmHPQX6r7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50913-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50913 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.7.0 --- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-11-07 13:07:53 UTC --- Looks like a genuine graphite bug though 718 switch (TREE_CODE (e)) 719 { 720 case POLYNOMIAL_CHREC: 721 scan_tree_for_params_right_scev (s, CHREC_RIGHT (e), 722 CHREC_VARIABLE (e), c); (gdb) call debug_generic_expr (e) {0B, +, (sizetype) pretmp.6_31}_2 632 | a [i * p] = ... */ 633 gcc_assert (TREE_CODE (e) == INTEGER_CST); where e here is CHREC_RIGHT (e). Looks like sth assumes this form of a SCEV does not happen. #(Data Ref: # bb: 4 # stmt: *dest_35 = D.2240_13; # ref: *dest_35; # base_object: *rptr_1; # Access function 0: {0B, +, (sizetype) pretmp.6_31}_2 #) Note that data-ref analysis fails with failed: evolution of base is not affine but graphite still forces access functions to be generated.
next prev parent reply other threads:[~2011-11-07 13:08 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-29 15:53 [Bug c/50913] New: ICE: compiling libgfortran for i686-w64-mingw32 vanboxem.ruben at gmail dot com 2011-10-29 22:36 ` [Bug middle-end/50913] " pinskia at gcc dot gnu.org 2011-10-30 15:21 ` vanboxem.ruben at gmail dot com 2011-11-07 11:44 ` [Bug middle-end/50913] [4.7 Regression] ICE in scan_tree_for_params_right_scev, at graphite-sese-to-poly.c:633 compiling libgfortran with -floop-interchange -m32 belyshev at depni dot sinp.msu.ru 2011-11-07 12:55 ` belyshev at depni dot sinp.msu.ru 2011-11-07 13:08 ` rguenth at gcc dot gnu.org [this message] 2011-12-06 13:55 ` rguenth at gcc dot gnu.org 2011-12-10 3:25 ` matt at use dot net 2011-12-12 10:17 ` rguenth at gcc dot gnu.org 2012-01-09 15:15 ` rguenth at gcc dot gnu.org 2012-01-09 15:33 ` [Bug tree-optimization/50913] " rguenth at gcc dot gnu.org 2012-01-10 9:16 ` rguenth at gcc dot gnu.org 2012-01-10 9:17 ` rguenth at gcc dot gnu.org 2013-07-21 9:23 ` spop at gcc dot gnu.org 2013-08-29 8:52 ` rguenth at gcc dot gnu.org
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-50913-4-QzmHPQX6r7@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).