This is the mail archive of the egcs-testresults@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
>Running target unix >FAIL: g77.f-torture/execute/u77-test.f execution, -O0 >FAIL: g77.f-torture/execute/u77-test.f execution, -O1 >FAIL: g77.f-torture/execute/u77-test.f execution, -O2 >FAIL: g77.f-torture/execute/u77-test.f execution, -O2 -fomit-frame-pointer -finline-functions >FAIL: g77.f-torture/execute/u77-test.f execution, -O2 -fomit-frame-pointer -finline-functions -funroll-loops >FAIL: g77.f-torture/execute/u77-test.f execution, -O2 -fomit-frame-pointer -finline-functions -funroll-all-loops >FAIL: g77.f-torture/execute/u77-test.f execution, -Os Could someone with an OpenBSD 2.5 (i386) system debug u77-test.f? It should be pretty easy -- it's probably calling abort() after noticing something wrong with the values returned by a libU77 routine. The more we g77 folk know about the problem, the more likely we can take it from there. tq vm, (burley)