Gpc November 2004

gpc@gnu.de

18 participants
22 discussions

Re: GCC integration?
by Waldek Hebisch 24 Nov '04

24 Nov '04

I wrote: > To have a comparison: I have not metered time spent hacking GPC, but > in the last year it is probably equivalent to 2-3 months. The above is about time _I_ have spent on GPC. I have not tried to quantify other contributions, so the total is much bigger. -- Waldek Hebisch hebisch(a)math.uni.wroc.pl

1 0

ia-64 test results with patch
by thomas.koenig＠bayertechnology.com 19 Nov '04

19 Nov '04

Hi everybody, thanks for pointing me to the 64-bit patch. Things are certainly looking better now. It's down to 26 unexpected failures now: === gpc tests === Running target any Running testsuite ... UNSUPPORTED: aregextest.pas UNSUPPORTED: asmtest.pas FAIL: casts2.pas FAIL: chief40.pas FAIL: emil21a.pas FAIL: emil21c.pas FAIL: emptyrec.pas FAIL: fieldw.pas FAIL: fjf129.pas FAIL: fjf23.pas FAIL: fjf30a.pas FAIL: fjf30b.pas FAIL: fjf327.pas FAIL: fjf347.pas FAIL: fjf512.pas FAIL: fjf526a.pas FAIL: fjf526b.pas FAIL: fjf666a.pas FAIL: fjf762a.pas FAIL: fjf9.pas FAIL: init1t.pas FAIL: math.pas FAIL: schema2a.pas FAIL: shl.pas FAIL: writeb.pas FAIL: writec.pas FAIL: writee.pas FAIL: writeg.pas === gpc Summary === # of tests 4044 # of expected passes 4016 # of unexpected failures 26 # of unsupported tests 2 /home/zfkts/zfkts/gpc-bin/gcc/xgpc version 20041017, based on gcc-3.3.3 make[1]: Leaving directory `/home/zfkts/zfkts/gpc-bin/gcc/p/test' $ grep -v OK test_log Test Run By zfkts on 2004-11-19 16:29:31 Native configuration is ia64-unknown-linux-gnu (byzrzd.bayer-ag.com) /home/zfkts/zfkts/gpc-bin/gcc/xgpc -B/home/zfkts/zfkts/gpc-bin/gcc/ 20041017, based on gcc-3.3.3, flags: -g -O3 -W -Wall -Wno-unused GPC-TEST-BEGIN ========================== TEST aregextest.pas: SKIPPED: librx not installed TEST asmtest.pas: SKIPPED: only for IA32 TEST casts2.pas: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/casts2.pas: In main program: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/casts2.pas:10: warning: cast to type of different size failed TEST chief40.pas: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/chief40.pas: In main program: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/chief40.pas:8: error: constant out of range /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/chief40.pas:11: error: arithmetical overflow /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/chief40.pas:11: error: constant overflow in expression /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/chief40.pas:14: error: arithmetical overflow /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/chief40.pas:14: error: constant overflow in expression failed TEST emil21a.pas: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21a.pas:12: error: invalid subrange type /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21a.pas:12: error: actual schema discriminant has invalid value /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21a.pas: In main program: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21a.pas:15: error: undeclared identifier `A' (first use in this routine) /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21a.pas:15: error: (Each undeclared identifier is reported only once /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21a.pas:15: error: for each routine it appears in.) failed TEST emil21c.pas: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21c.pas:12: error: invalid subrange type /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21c.pas:12: error: actual schema discriminant has invalid value /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21c.pas: In main program: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21c.pas:15: error: undeclared identifier `A' (first use in this routine) /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21c.pas:15: error: (Each undeclared identifier is reported only once /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/emil21c.pas:15: error: for each routine it appears in.) failed TEST emptyrec.pas: failed TEST fieldw.pas: failed (Foo) TEST fjf129.pas: Failed: 1.844674407370955e+19: 1.844674407370955e+19, 1.844674407370955e+19; 0.000000000000000e+00, 7.000000000000000e-01 TEST fjf23.pas: failed: 65534, 4294967294 TEST fjf30a.pas: failed: failed TEST fjf30b.pas: failed: failed TEST fjf327.pas: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf327.pas:4: error: arithmetical overflow /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf327.pas:4: error: constant overflow in expression /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf327.pas:4: error: constant out of range /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf327.pas:4: error: initial value is of wrong type /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf327.pas: In main program: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf327.pas:9: error: constant out of range failed TEST fjf347.pas: failed: 18446744073709551615 TEST fjf512.pas: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/test_run: line 335: 30623 Illegal instruction ./"$A_OUT" "$1" TEST fjf526a.pas: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf526a.pas: In main program: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf526a.pas:8: warning: left shift count >= width of type failed TEST fjf526b.pas: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf526b.pas: In main program: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf526b.pas:8: warning: left shift count >= width of type failed TEST fjf666a.pas: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf666a.pas: In main program: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf666a.pas:9: error: arithmetical overflow /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/fjf666a.pas:9: error: constant overflow in expression failed TEST fjf762a.pas: failed: TEST fjf9.pas: failed: 24 TEST init1t.pas: failed: failed TEST math.pas: 1,2c1 < it works !!! < /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/test_run: line 335: 27153 Illegal instruction ./"$A_OUT" "$1" --- > oh boyit works !!! failed TEST schema2a.pas: failed TEST shl.pas: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/shl.pas: In main program: /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/shl.pas:9: warning: left shift count >= width of type /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/shl.pas:11: warning: right shift count >= width of type /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/shl.pas:21: warning: left shift count >= width of type /home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/shl.pas:23: warning: right shift count >= width of type failed TEST writeb.pas: Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. TEST writec.pas: SP: LongInt `-7890123456789012345' was not indented, but should be. SP: LongInt `12345678901234567890' was not indented, but should be. SP: LongInt `-7890123456789012345' was not indented, but should be. SP: LongInt `12345678901234567890' was not indented, but should be. Run #1: LongInt `-7890123456789012345' was not indented, but should be. Run #1: LongInt `12345678901234567890' was not indented, but should be. Run #1: LongInt `-7890123456789012345' was not indented, but should be. Run #1: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. TEST writee.pas: EP: LongInt `-7890123456789012345' was not indented, but should be. EP: LongInt `12345678901234567890' was not indented, but should be. EP: LongInt `-7890123456789012345' was not indented, but should be. EP: LongInt `12345678901234567890' was not indented, but should be. EP: LongInt `-7890123456789012345' was not indented, but should be. EP: LongInt `12345678901234567890' was not indented, but should be. EP: LongInt `-7890123456789012345' was not indented, but should be. EP: LongInt `12345678901234567890' was not indented, but should be. Run #1: LongInt `-7890123456789012345' was not indented, but should be. Run #1: LongInt `12345678901234567890' was not indented, but should be. Run #1: LongInt `-7890123456789012345' was not indented, but should be. Run #1: LongInt `12345678901234567890' was not indented, but should be. Run #1: LongInt `-7890123456789012345' was not indented, but should be. Run #1: LongInt `12345678901234567890' was not indented, but should be. Run #1: LongInt `-7890123456789012345' was not indented, but should be. Run #1: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. TEST writeg.pas: Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #2: LongInt `-7890123456789012345' was not indented, but should be. Run #2: LongInt `12345678901234567890' was not indented, but should be. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #3: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #3: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. Run #4: LongInt `-7890123456789012345' was indented with field width 21, but should be with field width 44. Run #4: LongInt `12345678901234567890' was indented with field width 21, but should be with field width 44. ========================== GPC-TEST-END $ Thomas

1 0

test log for ia64
by thomas.koenig＠bayertechnology.com 19 Nov '04

19 Nov '04

Nice thing: the compiler does build, and it does some things. There are still some tests failing, though. Following is a test log. I have the complete gpc.log for anybody who's interested (I didn't include it because of its length). Thomas $ make check-pascal ../../gcc-3.3.3/gcc/p/script/mkdir-p p/test { \ echo "# Automatically generated from ../../gcc-3.3.3/gcc/p/test/Makefile."; \ echo "# Don't change manually."; \ echo ""; \ sed -e "s,^srcdir *=.*,srcdir=`cd ../../gcc-3.3.3/gcc/p/test && pwd`,; \ s,^PC *=.*,PC=`pwd`/xgpc -B`pwd`/,; \ s,^TEST_PATHS *=.*,TEST_PATHS=-I ../rts --unit-path=`cd ../../gcc-3.3.3/gcc/p/units && pwd`," \ ../../gcc-3.3.3/gcc/p/test/Makefile; \ } > p/test/Makefile || { rm -f p/test/Makefile; false; } echo timestamp > "p/stamp-test-Makefile" cd ./p/test && make MASK="" EXTRA_TEST_PFLAGS=" " TEST_RUN_FLAGS="" "pascal.check-dejagnu" make[1]: Entering directory `/home/zfkts/zfkts/gpc-bin/gcc/p/test' rm -f *.dat *.o *.s *.i *.gpi *.gpd *.gpc core a.out stderr.out *.exe testmake.tmp dummy.c dummy.pas dummy.out diff_cr*.tmp fixcr fixcr.exe rm -f todo/a.out todo/*.exe todo/*.o todo/*.s todo/*.i todo/*.gpi todo/*.gpd todo/core PC="/home/zfkts/zfkts/gpc-bin/gcc/xgpc -B/home/zfkts/zfkts/gpc-bin/gcc/" PFLAGS="-I ../rts --unit-path=/home/zfkts/zfkts/gcc-3.3.3/gcc/p/units --autobuild -g -O3 -W -Wall -Wno-unused " PFLAGS_NO_PATHS="-g -O3 -W -Wall -Wno-unused " SRCDIR="/home/zfkts/zfkts/gcc-3.3.3/gcc/p/test" TEST_MAKE_FLAG=test-make-flag "/home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/test_run" | tee test_log | "/home/zfkts/zfkts/gcc-3.3.3/gcc/p/test/test_sum" -d Test Run By zfkts on 2004-11-19 15:10:51 Native configuration is ia64-unknown-linux-gnu (byzrzd.bayer-ag.com) === gpc tests === Running target any Running testsuite ... UNSUPPORTED: aregextest.pas UNSUPPORTED: asmtest.pas FAIL: aturbo3test.pas FAIL: az43.pas FAIL: backtracerr.pas FAIL: bo4-10.pas FAIL: bo4-12.pas FAIL: bo4-14.pas FAIL: bo4-18.pas FAIL: bo5-17a.pas FAIL: bo5-17.pas FAIL: bo5-22.pas FAIL: casts2.pas FAIL: cfor.pas FAIL: chief31a.pas FAIL: chief31b.pas FAIL: chief31c.pas FAIL: chief31d.pas FAIL: chief40.pas FAIL: chuck6.pas FAIL: cntchars.pas FAIL: crttest.pas FAIL: dialec3.pas FAIL: dialec5.pas FAIL: dialec6.pas FAIL: dialec7.pas FAIL: eightqueens.pas FAIL: emil21a.pas FAIL: emil21c.pas FAIL: emptyrec.pas FAIL: expotst.pas FAIL: fay.pas FAIL: fieldw.pas FAIL: fjf125.pas FAIL: fjf129.pas FAIL: fjf168.pas FAIL: fjf172.pas FAIL: fjf181a.pas FAIL: fjf189.pas FAIL: fjf194a.pas FAIL: fjf194b.pas FAIL: fjf194c.pas FAIL: fjf194.pas FAIL: fjf23.pas FAIL: fjf246d.pas FAIL: fjf246e.pas FAIL: fjf254.pas FAIL: fjf257a.pas FAIL: fjf257b.pas FAIL: fjf257c.pas FAIL: fjf259.pas FAIL: fjf265.pas FAIL: fjf278.pas FAIL: fjf294a.pas FAIL: fjf306.pas FAIL: fjf30a.pas FAIL: fjf30b.pas FAIL: fjf320a.pas FAIL: fjf320b.pas FAIL: fjf323.pas FAIL: fjf327.pas FAIL: fjf343a.pas FAIL: fjf343b.pas FAIL: fjf347.pas FAIL: fjf354.pas FAIL: fjf359.pas FAIL: fjf375.pas FAIL: fjf380a.pas FAIL: fjf381.pas FAIL: fjf398.pas FAIL: fjf40b.pas FAIL: fjf40e.pas FAIL: fjf411.pas FAIL: fjf413h1.pas FAIL: fjf422.pas FAIL: fjf423.pas FAIL: fjf431.pas FAIL: fjf436b.pas FAIL: fjf436c.pas FAIL: fjf443.pas FAIL: fjf450b.pas FAIL: fjf450d.pas FAIL: fjf454.pas FAIL: fjf471.pas FAIL: fjf472.pas FAIL: fjf487b.pas FAIL: fjf488i2.pas FAIL: fjf488m2.pas FAIL: fjf488m3.pas FAIL: fjf488m4.pas FAIL: fjf488n2.pas FAIL: fjf488n3.pas FAIL: fjf488o2.pas FAIL: fjf488o4.pas FAIL: fjf488p2.pas FAIL: fjf488p4.pas FAIL: fjf496a4.pas FAIL: fjf496b4.pas FAIL: fjf496c4.pas FAIL: fjf496e4.pas FAIL: fjf501a.pas FAIL: fjf501b.pas FAIL: fjf509a.pas FAIL: fjf509b.pas FAIL: fjf512.pas FAIL: fjf516a.pas FAIL: fjf516b.pas FAIL: fjf524a.pas FAIL: fjf526a.pas FAIL: fjf526b.pas FAIL: fjf528a.pas FAIL: fjf528b.pas FAIL: fjf539a.pas FAIL: fjf574a.pas FAIL: fjf574b.pas FAIL: fjf574c.pas FAIL: fjf587f.pas FAIL: fjf619c.pas FAIL: fjf629g.pas FAIL: fjf636e.pas FAIL: fjf638.pas FAIL: fjf651a.pas FAIL: fjf651b.pas FAIL: fjf666a.pas FAIL: fjf675.pas FAIL: fjf68.pas FAIL: fjf732.pas FAIL: fjf753h.pas FAIL: fjf762a.pas FAIL: fjf768g.pas FAIL: fjf770.pas FAIL: fjf781a.pas FAIL: fjf781d.pas FAIL: fjf792a.pas FAIL: fjf792b.pas FAIL: fjf792g.pas FAIL: fjf792h.pas FAIL: fjf793a.pas FAIL: fjf793g.pas FAIL: fjf810.pas FAIL: fjf842.pas FAIL: fjf875c.pas FAIL: fjf923.pas FAIL: fjf9.pas FAIL: fnested.pas FAIL: fproc.pas FAIL: gale1c.pas FAIL: hamachi.pas FAIL: hanoi.pas FAIL: index.pas FAIL: insan.pas FAIL: jesper3.pas FAIL: math.pas FAIL: maur6.pas FAIL: miklos5.pas FAIL: nick1.pas FAIL: palindromes.pas FAIL: pat4.pas FAIL: permute.pas FAIL: pipetes2.pas FAIL: powersoftwo.pas FAIL: primes.pas FAIL: procvar3.pas FAIL: prx.pas FAIL: ptrvars.pas FAIL: pvs1.pas FAIL: random.pas FAIL: realout.pas FAIL: redef.pas FAIL: redefp.pas FAIL: rick1.pas FAIL: sam5.pas FAIL: scaltst.pas FAIL: schema2a.pas FAIL: sequin.pas FAIL: shl.pas FAIL: size.pas FAIL: slength.pas FAIL: steve1.pas FAIL: str2cstr.pas FAIL: strindex.pas FAIL: strini.pas FAIL: strptr1.pas FAIL: strptr2.pas FAIL: strptr3.pas FAIL: strptr4.pas FAIL: sven0.pas FAIL: sven15.pas FAIL: sven1.pas FAIL: sven4.pas FAIL: t04.pas FAIL: t08.pas FAIL: t09.pas FAIL: t10.pas FAIL: t11.pas FAIL: t15.pas FAIL: t17.pas FAIL: takashi1.pas FAIL: testio.pas FAIL: wnj.pas FAIL: writeb.pas FAIL: writec.pas FAIL: writee.pas FAIL: writeg.pas FAIL: writereal.pas === gpc Summary === # of tests 3999 # of expected passes 3794 # of unexpected failures 203 # of unsupported tests 2 /home/zfkts/zfkts/gpc-bin/gcc/xgpc version 20041017, based on gcc-3.3.3 make[1]: Leaving directory `/home/zfkts/zfkts/gpc-bin/gcc/p/test' $

2 1

null bytes on output with writeln
by thomas.koenig＠bayertechnology.com 19 Nov '04

19 Nov '04

There are leading null bytes on output with gpc-20041017. $ gpc -v Reading specs from /usr/local/lib/gcc-lib/ia64-unknown-linux-gnu/3.3.3/specs Configured with: ../gcc-3.3.3/configure --enable-languages=c,p : (reconfigured) ../gcc-3.3.3/configure --enable-languages=c,pascal Thread model: posix gpc version 20041017, based on gcc-3.3.3 $ cat nullbytes.pas program main; begin writeln(1.0:20:10); end. $ gpc nullbytes.pas $ ./a.out | od -x 0000000 0000 0000 2020 2020 2e31 3030 3030 3030 0000020 3030 3030 000a 0000025 I'd prefer if there were spaces :-) Regards Thomas

2 1

PGCC
by Silvio a Beccara 17 Nov '04

17 Nov '04

Hi, I just found about PGCC, a version of GCC specially optimised for Pentium processors. Anybody ever thought about making GPC work using PGCC as a backend, so as to take profit of the (supposed) optimisations and speed gain? Regards Silvio a Beccara

2 1

working with char driver as with the file in GPC
by Igor Marnat 16 Nov '04

16 Nov '04

Hello dear List! Unfortunately there is no possibility at the moment to search through list-archives. Perhaps someone could give me an advise. I'd like to communicate with the char device driver which is realised as a file. In C I can just make "dsp_fd = open(dsp_devname, O_RDWR|O_SYNC)" and then work with it all the time using "write(fd, (const void*)msg, nbytes)" and read respectively without additional activities. How should I use it in GPC? The only way I see is to Assign (dsp_fd, dsp_devname) and then Rewrite it when I have to write to and Reset it when I need to read from. Is it the right way from the point of view of the system performance? Or should I better create an interface with file written in C to avoid the Reset and Rewrite operations? Thanks, regards, Igor mailto:marny@rambler.ru

2 3

gpc-20041017 binaries for Mingw and Fedora Core 2 (AMD-64 )
by Prof A Olowofoyeku (The African Chief) 15 Nov '04

15 Nov '04

Hi I have released binaries for gpc-20041017 for these platforms: Mingw (Win32) MSYS (Win32-posix) Fedora Core 2 for AMD-64 Also released is Dev+GNU Pascal (a Full GPL Pascal Programming Environment + Win32 IDE) v1.94.4, based on gpc-20041017 and an updated Dev-Pascal IDE. Check here for downloads: http://www.gnu-pascal.de/contrib/chief/ Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/

4 4

unbalanced comment bug
by Russell Whitaker 13 Nov '04

13 Nov '04

Hi Found a rather trivial bug, shown here as { { }, the original was a typo: { ) { }. ( so I need new glasses ). program bug; begin { this writeln("OK"); exit; { is a bug } writeln("fail"); end. Russ p.s. built gpc with gcc-3.3.5, no errors in test suite. good.

2 1

xcode and gpc?
by P. George 12 Nov '04

12 Nov '04

i've got xcode. i've got gpc. how can i get them to kiss? - philip

2 2

GPC web site is back
by Frank Heckenbach 10 Nov '04

10 Nov '04

Hi everybody, I am happy to announce that the GPC web site <http://www.gnu-pascal.de> is back online, after several weeks of problems on the server. The current GPC beta release (20041017) is on the download page. Previous alphas/betas between 2.1 and this one have been omitted since I'd have to reconstruct them from my archives and verify them to be trushworthy, and I don't think it's worth the effort. If there are serious problems with 20041017, I'd rather fix them, so everyone can ugprade. Thanks to Eike Lange and Benedikt Wildenhain for helping set up the server again and to G-N-U GmbH for hosting the current GPC beta release in the meantime. Frank -- Frank Heckenbach, frank(a)g-n-u.de http://fjf.gnu.de/ GnuPG and PGP keys: http://fjf.gnu.de/plan (7977168E)

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

Gpc November 2004