public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/38280] [4.4 regression] Revision 142207 breaks 416.gamess/481.wrf in SPEC CPU 2006 Date: Thu, 27 Nov 2008 20:33:00 -0000 [thread overview] Message-ID: <20081127203221.13772.qmail@sourceware.org> (raw) In-Reply-To: <bug-38280-682@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from vmakarov at redhat dot com 2008-11-27 20:32 ------- The problem was in violation of allocno order in regno_allocno_map list. This order is very important for many algorithms (allocno info propagation, conflict propagation and IR flattening). For example, loop 0: no usage of R loop 1: a1 representing R loop 2: a2 representing R After removing Loop1, we move a1 to loop 0. Allocnos on upper levels should be after allocnos on lower levels in regno_allocno_map list. Before removing loop we had a1 a2 in the list which is ok because they are on the same loop level. After removing loop 1, we have again a1 and a2 which is not ok because a1 now corresponds to loop 0 containing loop 1 and as a consequence should be after a2. We had no problem before the patch because we removed always a loop and all its subloops (removing loops based on register pressure) and the order violation was not possible. I'll submit a patch solving the problem today. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38280
next prev parent reply other threads:[~2008-11-27 20:33 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-26 19:00 [Bug rtl-optimization/38280] New: [4.3 Regression] Revision 142207 breaks 416.gamess/481.wrf/ " hjl dot tools at gmail dot com 2008-11-27 17:33 ` [Bug rtl-optimization/38280] [4.4 regression] Revision 142207 breaks 416.gamess/481.wrf " jsm28 at gcc dot gnu dot org 2008-11-27 20:33 ` vmakarov at redhat dot com [this message] 2008-11-27 23:31 ` hjl at gcc dot gnu dot org 2008-11-28 3:41 ` Joey dot ye at intel dot com 2008-11-28 8:43 ` hjl dot tools at gmail dot com 2008-11-28 15:12 ` Joey dot ye at intel dot com 2008-11-28 15:22 ` hjl dot tools at gmail dot com 2008-12-01 2:19 ` Joey dot ye at intel dot com 2008-12-02 0:18 ` vmakarov at gcc dot gnu dot org 2008-12-02 18:50 ` hjl dot tools 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=20081127203221.13772.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).