Gpc

gpc@gnu.de

5400 discussions

Re: your mail
by Tom Schneider 02 Dec '04

02 Dec '04

Pete, Tod: > GPC: daily digest > > This is Digest Volume 1 : Issue 587 : Digest Style "text" > Below is a summary of all the messages, showing the subject of each post > and who posted it, followed by the full text of all messages. > > internal compiler error: in find_function_data, at function.c:317 > Re: internal compiler error: in find_function_data, at function.c:317 > > ---------------------------------------------------------------------- > > Date: Wed, 1 Dec 2004 19:27:16 -0600 > From: "Fiedler, Todd, A" <tafiedler(a)cmh.edu> > To: <gpc(a)gnu.de> > Subject: internal compiler error: in find_function_data, at function.c:317 > Message-ID: <958B228E6A626242A3FEAB621C4C933504B12A0D(a)exch2000.cmh.internal> > > REVISION -- Note: I included the lister.i file as a zip because it is over > 11,000 lines long. > > Hello. I am attempting to compile a program named lister.p, that does > some genomic work. I can compile some programs in this suite while > others always generate an error. I'm not much of a pascal programmer, > it's been 15 years since I actually wrote anything in it, but a group of > researchers here would like to get this working. Any help will be very > much appreciated! > > Thanks! > Todd > > > I am compiling on Mac OS X. Here are my specs. > > $ uname -a > Darwin seed.cmh.edu 7.6.0 Darwin Kernel Version 7.6.0: Sun Oct 10 > 12:05:27 PDT 2004; root:xnu/xnu-517.9.4.obj~1/RELEASE_PPC Power > Macintosh powerpc > > $ gcc -v > Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs > Thread model: posix > gcc version 3.3 20030304 (Apple Computer, Inc. build 1666) > > $ gpc -v > > Reading specs from > /Developer/Pascal/gpc332d1/lib/gcc-lib/powerpc-apple-darwin/3.3.2/specs > Configured with: ../gpc-332d1/configure --enable-languages=pascal,c > --prefix=/Developer/Pascal/gpc332d1 --enable-threads=posix > --target=powerpc-apple-darwin Thread model: posix gpc version 20030830, > based on gcc-3.3.2 > > > I ran gpc with the following command line: > > gpc -x Pascal -save-temps lister.p -o lister > > lister.p: In procedure `showpiece': > lister.p:7730: internal compiler error: in find_function_data, at > function.c:317 Please submit a full bug report, with preprocessed source > if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. > > > > [Attachment of type application/zip removed.] > > ------------------------------ > > Date: Thu, 2 Dec 2004 03:43:39 +0100 > From: Adriaan van Os <gpc(a)microbizz.nl> > To: gpc(a)gnu.de > Subject: Re: internal compiler error: in find_function_data, at function.c:317 > Message-ID: <F8EDEB53-440B-11D9-BAA2-000A27944772(a)microbizz.nl> > > Fiedler, Todd, A wrote: > > > lister.p: In procedure `showpiece': > > lister.p:7730: internal compiler error: in find_function_data, at > > function.c:317 Please submit a full bug report, with preprocessed > > source > > if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for > > instructions. > > Reproducable with the latest gpc sources on Mac OS X. > > Regards, > > Adriaan van Os > > > > ------------------------------ > > End of > ********** Unfortunately this appears to be a release of the source code for sequence walkers. However, it says "Attachment of type application/zip removed." Does that mean it appeared in the archive but not the mailing list? Tom

2 1

Re: your mail
by Tom Schneider 02 Dec '04

02 Dec '04

Pete: > Todd will make sure that any lister code is scrubbed from the site. > As you are aware, this was an internal error, due to modifications > of the gpc Pascal compiler and not an error in the lister code > itself. Thanks. I recognize why Todd did this, appreciate his efforts and normally it would be ok. I also recognize that we are stuck if the GPC compiler fails on lister, so it is important to have GPC working properly. It is not clear how to handle this without a general release, but perhaps a release only to the people who know how to deal with it would be appropriate. Since we just had a system upgrade but didn't change GPC, I suspect that this is a system library problem. Tom

1 0

internal compiler error: in find_function_data, at function.c:317
by Fiedler, Todd, A 02 Dec '04

02 Dec '04

REVISION -- Note: I included the lister.i file as a zip because it is over 11,000 lines long. Hello. I am attempting to compile a program named lister.p, that does some genomic work. I can compile some programs in this suite while others always generate an error. I'm not much of a pascal programmer, it's been 15 years since I actually wrote anything in it, but a group of researchers here would like to get this working. Any help will be very much appreciated! Thanks! Todd I am compiling on Mac OS X. Here are my specs. $ uname -a Darwin seed.cmh.edu 7.6.0 Darwin Kernel Version 7.6.0: Sun Oct 10 12:05:27 PDT 2004; root:xnu/xnu-517.9.4.obj~1/RELEASE_PPC Power Macintosh powerpc $ gcc -v Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs Thread model: posix gcc version 3.3 20030304 (Apple Computer, Inc. build 1666) $ gpc -v Reading specs from /Developer/Pascal/gpc332d1/lib/gcc-lib/powerpc-apple-darwin/3.3.2/specs Configured with: ../gpc-332d1/configure --enable-languages=pascal,c --prefix=/Developer/Pascal/gpc332d1 --enable-threads=posix --target=powerpc-apple-darwin Thread model: posix gpc version 20030830, based on gcc-3.3.2 I ran gpc with the following command line: gpc -x Pascal -save-temps lister.p -o lister lister.p: In procedure `showpiece': lister.p:7730: internal compiler error: in find_function_data, at function.c:317 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions.

4 3

GPC on AIX - memory limit?
by Peter Keenan 29 Nov '04

29 Nov '04

Hi, I've built gpc 20041017, based on gcc-3.3.2 in my home directory on an AIX machine which has the GCC 3.3.2 binaries installed in usr/local/bin. The testsuite programs all run fine and I am able to compile and run my own programs. I am using a program converted from Delphi, where I increased the stack and heap limits to allow the program use more memory. The program ran successfully several times on a PC, using more than 1GB of memory. However on AIX the program seem to be hitting a ceiling as they crash out with SIGILL, this happened with several datasets. The crash occurs at a New() statement asking for an additional 1600 bytes of memory and seems to occur when about 256MB of memory has been used. I tried the memavail function and it shows around 256 MB available at the start of the program, however memavail also sometimes causes a segmentation fault so I cannot use it to plot the memory use of the program . Using ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited max memory size (kbytes, -m) unlimited open files (-n) unlimited pipe size (512 bytes, -p) 64 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 10000 virtual memory (kbytes, -v) unlimited so no obviou problem there., If I use ulimit -d to reduce the data size below 256MB then that affects the program, but increasing it to a fixed value above 256MB does not seem to stop it crashing. I am inexperienced with the UNIX type environment and would appreciate any suggestions for changes needed at the GPC end or at the AIX and to get around this problem. Peter.

2 2

-Wno-underscore
by Adriaan van Os 28 Nov '04

28 Nov '04

[G4:~/testgpcadriaan] adriaan% cat NoUnderscore.p program NoUnderscore; procedure _Run; begin writeln('_Run') end; begin _Run end. [G4:~/testgpcadriaan] adriaan% gpc NoUnderscore.p NoUnderscore.p:4: warning: identifiers should not start with an underscore [G4:~/testgpcadriaan] adriaan% gpc NoUnderscore.p -Wno-underscore [G4:~/testgpcadriaan] adriaan% gpc NoUnderscore.p --gnu-pascal -Wno-underscore NoUnderscore.p:4: warning: identifiers should not start with an underscore So, it seems that -Wno-underscore is broken when used with --gnu-pascal. Regards, Adriaan van Os

4 6

Re: Building GPC with GCC 3.4.2 (in Fedora Core 3)
by Wood David 24 Nov '04

24 Nov '04

A big thanks Waldek. I seem to have a gpc built with gcc 3.4.2. Just a few minor hiccups which don't appear to have been too critical: 1) The man pages didn't build because help2man wasn't found. I'm not sure where this normally comes from, but the man pages have usually been built ok. 2) When I did 'cd gcc' and 'make pascal.install-with-gcc' , the gpc -v command gave me the correct build version, but a gpc compilation resulted in the error 'installation problem, cannot exec gpc1: no such file or directory'. Repeating the installation just using 'make install' solved the problem. 3) At the end of the install, I get the error /bin/sh: -ranlib: command not found. I presume the leading '-' is messing this up. I found ranlib in /usr/bin. Apologies for the corporate nonsense that follows. I'll try to get our company policy changed but it's likely to be a David and Goliath battle! Regards David. > -----Original Message----- > From: gpc-owner(a)gnu.de [mailto:gpc-owner@gnu.de]On Behalf Of Waldek > Hebisch > Sent: Wednesday, November 24, 2004 2:08 PM > To: gpc(a)gnu.de > Subject: Re: Building GPC with GCC 3.4.2 (in Fedora Core 3) > > > Wood David wrote: > > I'm trying to compile gpc-20040516 with gcc-core-3.4.2 in > the hope it will > > sort out a compatibility problem when linked with other > c-code we've built. > > I found Waldek's patches to gpc proper and gcc 3.4.20041015 > (I've also tried > > the 3.4.0 patch) and applied these using $ patch -p1 < > XX.diff in the > > respective source directories. However, the make crashes, > firstly with > > > > ../../gcc-3.4.2/gcc/p/mk_lang_opt: Permission denied. > > > > In normal build `mk_lang_opt' should not run (it is needed only after > a modification). The problem is due to limitation of `patch' (inabilty > to set file mode or modification time) and microsecond timestamps > in new kernels. Before the build you should touch `lang.opt' and > `handle-opts.c' to mark them as up to date. > > > So I do a chmod +x on this file and type make again. The > next worry comes > > when it says I should have 16 shift/reduce conflicts and 30 > reduce/reduce > > conflicts but I get 16 and 295! > > > > That is harmless. > > > The final nail in the coffin appears when p/handle-opts.c > produces a string > > of errors because the OPT_* components are undeclared. > Just before this, > > lang.c reports a number of warnings about function > declarations not being > > prototypes and no previous prototype for 'pascal_post-options' or > > 'pascal_handle_option'. > > > > Trying to run `mk_lang_opt' had wiped-out pre-built `lang.opt' (you > get empty file instead). `lang.opt' is needed to define > `OPT_*' constants. > Making `mk_lang_opt' executable _before_ the build should also correct > the problem. > > -- > Waldek Hebisch > hebisch(a)math.uni.wroc.pl > The Information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful. Emails and other electronic communication with QinetiQ may be monitored. Calls to QinetiQ may be recorded for quality control, regulatory and monitoring purposes.

1 0

Building GPC with GCC 3.4.2 (in Fedora Core 3)
by Wood David 24 Nov '04

24 Nov '04

I'm trying to compile gpc-20040516 with gcc-core-3.4.2 in the hope it will sort out a compatibility problem when linked with other c-code we've built. I found Waldek's patches to gpc proper and gcc 3.4.20041015 (I've also tried the 3.4.0 patch) and applied these using $ patch -p1 < XX.diff in the respective source directories. However, the make crashes, firstly with ../../gcc-3.4.2/gcc/p/mk_lang_opt: Permission denied. So I do a chmod +x on this file and type make again. The next worry comes when it says I should have 16 shift/reduce conflicts and 30 reduce/reduce conflicts but I get 16 and 295! The final nail in the coffin appears when p/handle-opts.c produces a string of errors because the OPT_* components are undeclared. Just before this, lang.c reports a number of warnings about function declarations not being prototypes and no previous prototype for 'pascal_post-options' or 'pascal_handle_option'. Am I doing something silly? I've been building gpc with gcc-3.3.2 without any difficulty. Regards David Wood QinetiQ Farnborough The Information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful. Emails and other electronic communication with QinetiQ may be monitored. Calls to QinetiQ may be recorded for quality control, regulatory and monitoring purposes.

3 2

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

Jump to page:

2025

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