public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/44785]  New: [4.6 Regression] FAIL: gfortran.dg/extends_3.f03
@ 2010-07-02 16:05 hjl dot tools at gmail dot com
  2010-07-03  2:47 ` [Bug middle-end/44785] [4.6 Regression] Invalid memory access in gfortran.dg/extends_3.f03 hjl dot tools at gmail dot com
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: hjl dot tools at gmail dot com @ 2010-07-02 16:05 UTC (permalink / raw)
  To: gcc-bugs

On Linux/x86, I saw

FAIL: gfortran.dg/extends_3.f03  -O1  (internal compiler error)
FAIL: gfortran.dg/extends_3.f03  -O1  (test for excess errors)

come and go, at least starting from revision 161653.


-- 
           Summary: [4.6 Regression] FAIL: gfortran.dg/extends_3.f03
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hjl dot tools at gmail dot com


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


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

end of thread, other threads:[~2010-07-04 12:21 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-07-02 16:05 [Bug middle-end/44785] New: [4.6 Regression] FAIL: gfortran.dg/extends_3.f03 hjl dot tools at gmail dot com
2010-07-03  2:47 ` [Bug middle-end/44785] [4.6 Regression] Invalid memory access in gfortran.dg/extends_3.f03 hjl dot tools at gmail dot com
2010-07-03  3:51 ` hjl dot tools at gmail dot com
2010-07-03 10:33 ` rguenth at gcc dot gnu dot org
2010-07-04 10:15 ` rguenth at gcc dot gnu dot org
2010-07-04 12:20 ` rguenth at gcc dot gnu dot org
2010-07-04 12:21 ` rguenth 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).