This is the mail archive of the
egcs-testresults@egcs.cygnus.com
mailing list for the EGCS project.
Re: Results for gcc-2.95 19990609 (prerelease) testsuite on i586-cygwin32
- To: egcs-testresults@egcs.cygnus.com
- Subject: Re: Results for gcc-2.95 19990609 (prerelease) testsuite on i586-cygwin32
- From: Mumit Khan <khan@xraylith.wisc.EDU>
- Date: Fri, 11 Jun 1999 13:22:00 -0500 (CDT)
On Fri, 11 Jun 1999, Jeffrey A Law wrote:
> In message <c96e169d.2491f041@aol.com>you write:
> > In a message dated 99-06-11 00:43:06 EDT, khan@xraylith.wisc.EDU writes:
> >
> > << FAIL: g77.f-torture/compile/19990502-0.f, -O2
> > FAIL: g77.f-torture/compile/19990502-0.f, -O2 -fomit-frame-pointer
> > -finline-functions
> > FAIL: g77.f-torture/compile/19990502-0.f, -Os
> > FAIL: g77.f-torture/compile/19990502-0.f, -O2
> > FAIL: g77.f-torture/compile/19990502-0.f, -O2 -fomit-frame-pointer
> > -finline-functions
> > FAIL: g77.f-torture/compile/19990502-0.f, -Os
> > >>
> > Are these time-out failures? I see most of these when running the tests on
> > an NT FAT16 file system, which is excruciatingly slow, but not with faster
> > combinations like W95/FAT32 or W2K/NTFS5.
> Highly unlikely. We already know what this bug is, we just haven't fixed it
> yet.
Tim may be running into cygwin/expect problems, which there are many. I
use a extremely hacked setup using Gordon Chaffee's Expect/NT and
slightly modified dejagnu to do the testing, and then run random spot
checks to make sure Expect/NT is doing the wrong thing. I did check
these by hand and Jeff and Craig are correct that these should show up
as failures.
Regards,
Mumit