public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/50124] New: gfortran.dg/graphite/interchange-1.f XPASSes everywhere
@ 2011-08-19 13:25 ro at gcc dot gnu.org
  2011-08-22  9:32 ` [Bug tree-optimization/50124] " burnus at gcc dot gnu.org
  2011-08-29 16:23 ` ro at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: ro at gcc dot gnu.org @ 2011-08-19 13:25 UTC (permalink / raw)
  To: gcc-bugs

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

             Bug #: 50124
           Summary: gfortran.dg/graphite/interchange-1.f XPASSes
                    everywhere
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ro@gcc.gnu.org
                CC: spop@gcc.gnu.org
              Host: *-*-solaris2.*, mips-sgi-irix6.5
            Target: *-*-solaris2.*, mips-sgi-irix6.5
             Build: *-*-solaris2.*, mips-sgi-irix6.5


Since 20110805, the gfortran.dg/graphite/interchange-1.f test seems to XPASS
everywhere.  Is this expected and can the xfail be removed to reduce testsuite
noise?

  Rainer


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

* [Bug tree-optimization/50124] gfortran.dg/graphite/interchange-1.f XPASSes everywhere
  2011-08-19 13:25 [Bug tree-optimization/50124] New: gfortran.dg/graphite/interchange-1.f XPASSes everywhere ro at gcc dot gnu.org
@ 2011-08-22  9:32 ` burnus at gcc dot gnu.org
  2011-08-29 16:23 ` ro at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: burnus at gcc dot gnu.org @ 2011-08-22  9:32 UTC (permalink / raw)
  To: gcc-bugs

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu.org

--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-08-22 09:30:35 UTC ---
I have committed a patch for that - w/o seeing this PR, cf.
http://gcc.gnu.org/ml/fortran/2011-08/msg00174.html - I think it was fixed with
the patch for PR 49957.


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

* [Bug tree-optimization/50124] gfortran.dg/graphite/interchange-1.f XPASSes everywhere
  2011-08-19 13:25 [Bug tree-optimization/50124] New: gfortran.dg/graphite/interchange-1.f XPASSes everywhere ro at gcc dot gnu.org
  2011-08-22  9:32 ` [Bug tree-optimization/50124] " burnus at gcc dot gnu.org
@ 2011-08-29 16:23 ` ro at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: ro at gcc dot gnu.org @ 2011-08-29 16:23 UTC (permalink / raw)
  To: gcc-bugs

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

Rainer Orth <ro at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                URL|                            |http://gcc.gnu.org/ml/gcc-p
                   |                            |atches/2011-08/msg01628.htm
                   |                            |l
         Resolution|                            |FIXED
   Target Milestone|---                         |4.7.0

--- Comment #2 from Rainer Orth <ro at gcc dot gnu.org> 2011-08-29 16:16:33 UTC ---
Fixed for 4.7.0.


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

end of thread, other threads:[~2011-08-29 16:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-08-19 13:25 [Bug tree-optimization/50124] New: gfortran.dg/graphite/interchange-1.f XPASSes everywhere ro at gcc dot gnu.org
2011-08-22  9:32 ` [Bug tree-optimization/50124] " burnus at gcc dot gnu.org
2011-08-29 16:23 ` ro at gcc dot gnu.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).