public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/38953]  New: [graphite] loop closed SSA not maintained by graphite code generation
@ 2009-01-24  0:32 spop at gcc dot gnu dot org
  2009-01-24  0:48 ` [Bug tree-optimization/38953] " spop at gcc dot gnu dot org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: spop at gcc dot gnu dot org @ 2009-01-24  0:32 UTC (permalink / raw)
  To: gcc-bugs

This problem happened in the graphite branch where after the graphite
pass we scheduled a pass of loop invariant motion (LIM).  LIM does
expect to see the loop closed SSA form, but that property is not
maintained by the code generator of graphite.  The testcase is
extracted from the polyhedron benchmark aermod.f90 and it failed on
graphite branch when compiled with -O3 that implies -floop-block and
-fgraphite-identity.


-- 
           Summary: [graphite] loop closed SSA not maintained by graphite
                    code generation
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: spop at gcc dot gnu dot org
        ReportedBy: spop at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38953


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2009-02-09 20:35 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-01-24  0:32 [Bug tree-optimization/38953] New: [graphite] loop closed SSA not maintained by graphite code generation spop at gcc dot gnu dot org
2009-01-24  0:48 ` [Bug tree-optimization/38953] " spop at gcc dot gnu dot org
2009-01-24  1:00 ` spop at gcc dot gnu dot org
2009-01-24  1:00 ` spop at gcc dot gnu dot org
2009-02-05 21:45 ` spop at gcc dot gnu dot org
2009-02-09 20:35 ` spop at gcc dot gnu dot org

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).