The following test results were obtained with gpc version 20030507, based on gcc-3.2.3 (mingw special 20030504-1), configured for i486-pc-mingw32:
------------------
TEST agettext2test.pas: SKIPPED: libintl not installed TEST crttest.pas: SKIPPED: no curses library found TEST dialec3.pas: ./../units/dos.pas: In procedure `GetCBreak': ./../units/dos.pas:704: warning: suggest parentheses around `and' in operand of `<>' OK TEST dialec6.pas: ./../units/dos.pas: In procedure `GetCBreak': ./../units/dos.pas:704: warning: suggest parentheses around `and' in operand of `<>' OK TEST dostest.pas: gpc1.exe: warnings being treated as errors ./../units/dos.pas: In procedure `GetCBreak': ./../units/dos.pas:704: warning: suggest parentheses around `and' in operand of `<>' gpc1.exe: F:\Programming\GNU\root\usr\local\gpc-mingw\bin\gpc.exe exited with status 1 failed TEST dostest2.pas: gpc1.exe: warnings being treated as errors ./../units/dos.pas: In procedure `GetCBreak': ./../units/dos.pas:704: warning: suggest parentheses around `and' in operand of `<>' gpc1.exe: F:\Programming\GNU\root\usr\local\gpc-mingw\bin\gpc.exe exited with status 1 failed TEST environo.pas: SKIPPED: setenv not present in libc TEST fjf480a.pas: SKIPPED: librx not installed TEST fjf480b.pas: SKIPPED: librx not installed TEST fjf663.pas: SKIPPED: IOSelectRead not supported on this system TEST gettexttest.pas: SKIPPED: libintl not installed TEST gmptest.pas: SKIPPED: libgmp not installed TEST pipetes2.pas: Unexpected output `Unexpected output `Unexpected output `Unexpected output `Unexpected output [...] TEST pipetest.pas: SKIPPED: IOSelect not yet implemented for mingw TEST regextest.pas: SKIPPED: librx not installed TEST windtes2.pas: gpc1.exe: warnings being treated as errors ./../units/dos.pas: In procedure `GetCBreak': ./../units/dos.pas:704: warning: suggest parentheses around `and' in operand of `<>' gpc1.exe: F:\Programming\GNU\root\usr\local\gpc-mingw\bin\gpc.exe exited with status 1 gpc1.exe: F:\Programming\GNU\root\usr\local\gpc-mingw\bin\gpc.exe exited with status 1 failed TEST windtest.pas: gpc1.exe: warnings being treated as errors ./../units/dos.pas: In procedure `GetCBreak': ./../units/dos.pas:704: warning: suggest parentheses around `and' in operand of `<>' gpc1.exe: F:\Programming\GNU\root\usr\local\gpc-mingw\bin\gpc.exe exited with status 1 failed TEST y2k.pas: gpc1.exe: warnings being treated as errors ./../units/dos.pas: In procedure `GetCBreak': ./../units/dos.pas:704: warning: suggest parentheses around `and' in operand of `<>' gpc1.exe: F:\Programming\GNU\root\usr\local\gpc-mingw\bin\gpc.exe exited with status 1 failed
# of GPC tests 3594 # of GPC tests passed 3576 # of GPC tests skipped 10 # of GPC tests failed 8
------------------
Suppression of the warning suggesting parentheses or repair of the associated source file would eliminate 7 of the 8 failing tests (note that "dialec3.pas" and "dialec6.pas" report "OK" but apparently are counted as failing tests).
The "pipetes2.pas" test outputs "`Unexpected output " repeatedly until 2048 characters are printed. I have trimmed the text for this report.
To compile gpc using gcc-3.2.3, the change described by Russ Whitaker in his message of 7th June 2003 (to line 42 of p/config-lang.in) was needed.
-- Dave
J. David Bryan wrote:
TEST dialec3.pas: ./../units/dos.pas: In procedure `GetCBreak': ./../units/dos.pas:704: warning: suggest parentheses around `and' in operand of `<>' OK
Suppression of the warning suggesting parentheses or repair of the associated source file would eliminate 7 of the 8 failing tests
Thanks, will do.
(note that "dialec3.pas" and "dialec6.pas" report "OK" but apparently are counted as failing tests).
A test is counted as passed only if it writes "OK" and nothing else.
TEST pipetes2.pas: Unexpected output `Unexpected output `Unexpected output `Unexpected output `Unexpected output [...]
The "pipetes2.pas" test outputs "`Unexpected output " repeatedly until 2048 characters are printed. I have trimmed the text for this report.
Pipes have never worked well under Windows. There are known problems (though not this one so far, AFAIK). If someone wants to try debugging it, I could perhaps offer some hints ...
Frank
On 7 Jul 2003 at 5:05, Frank Heckenbach wrote:
Pipes have never worked well under Windows. There are known problems (though not this one so far, AFAIK). If someone wants to try debugging it, I could perhaps offer some hints ...
I have taken a very quick look at this (pipetes2.pas), and what appears to happen is that the "Parameters" are not being passed correctly to the newly created process, so that process creates another, and another, and another.... Eventually, something fails, and each process prints "Unexpected output" as the list of processes unwinds.
I'll look into this more deeply this weekend.
-- Dave
-
Frank Heckenbach -
J. David Bryan