public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "irar at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/21218] [4.1 regression] ICE using -ftree-vectorize Date: Tue, 26 Apr 2005 10:24:00 -0000 [thread overview] Message-ID: <20050426100502.30216.qmail@sourceware.org> (raw) In-Reply-To: <20050425143552.21218.reichelt@gcc.gnu.org> ------- Additional Comments From irar at il dot ibm dot com 2005-04-26 10:04 ------- We get the following code for the loop: this_5 = &b_4->D.2068; D.2080_9 = this_5->d[i_18]; b_4->D.2068.d[i_18] = D.2080_9; In analysis of data-ref this_5->d[i_18] we don't check that the initial condition of access_fn of *this_5 is not loop invariant (we rely on evolution == NULL test, which is wrong). This is already fixed in autovect branch, and I am working on a patch to bring the changes in data-refs analysis to mainline. Another issue here is that this_5 = &b_4->D.2068; is loop invariant and can be hoist out of the loop. Maybe it will happen with structure-aliasing-branch? -- What |Removed |Added ---------------------------------------------------------------------------- CC| |dberlin at gcc dot gnu dot | |org AssignedTo|unassigned at gcc dot gnu |irar at il dot ibm dot com |dot org | Status|NEW |ASSIGNED Last reconfirmed|2005-04-25 14:43:35 |2005-04-26 10:04:49 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21218
next prev parent reply other threads:[~2005-04-26 10:24 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-25 14:37 [Bug tree-optimization/21218] New: " reichelt at gcc dot gnu dot org 2005-04-25 14:43 ` [Bug tree-optimization/21218] " pinskia at gcc dot gnu dot org 2005-04-26 10:24 ` irar at il dot ibm dot com [this message] 2005-04-28 16:24 ` pinskia at gcc dot gnu dot org 2005-05-20 16:56 ` reichelt at gcc dot gnu dot org 2005-05-20 17:22 ` hubicka at ucw dot cz 2005-06-28 23:11 ` bangerth at dealii dot org 2005-06-28 23:23 ` bangerth at dealii dot org 2005-06-29 13:37 ` reichelt at gcc dot gnu dot 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=20050426100502.30216.qmail@sourceware.org \ --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).