Gpc

gpc@gnu.de

5400 discussions

Windows install
by Jay Michael 17 Jul '12

17 Jul '12

Where is the source corresponding to GPC 20070904? Where should I find the .gpi files for supplied units (like unit GPC)? If I install a binary distribution for Windows, is there a follow-up step that must be performed manually? (like compiling GPC.PAS) Where would I find documentation of the entry points provided by unit GPC? I downloaded and installed dev_gnu_pascal-1.9.4.13.exe I started with mingw-get-inst-20120426.exe -- It downloaded and installed whatever it wanted. From the size of dev_gnu_pascal-1.9.4.13.exe I had assumed it included the source of GPC, but I haven't been able to find it. In http://www.gnu-pascal.de/alpha, there is no gcc-core-3.4.5, and there is no gpc-20070904.

3 4

unit/procedure same name, unhelpful error
by Jay Michael 10 Jul '12

10 Jul '12

gpc 20070904, based on gcc-3.4.5 (mingw special) I got a compilation error, "expression used as a statement". When I finally realized I had a unit and a procedure in the unit with the same name, I changed one name and the error went away, so I'm guessing the duplication of name was somehow responsible. I am not asking to be allowed to name a unit the same as some entity within the unit. I am asking that the error message be changed to something that would have spared me thrashing around until I noticed that I had duplicated a name. Failing that, could someone explain how what I did was an "expression used as a statement"? >gpc -c -x Pascal jsm2m.int >gpc -c jsm2.pas jsm2.pas: In main program: jsm2.pas:5: error: expression used as a statement

2 1

Re: string literal as const var parameter
by Waldek Hebisch 10 Jul '12

10 Jul '12

> > > From: Waldek Hebisch <hebisch(a)math.uni.wroc.pl> > > Subject: Re: string literal as const var parameter > > To: "Jay Michael" <jmichael_ll(a)yahoo.com> > > Cc: gpc(a)gnu.de > > Date: Monday, July 9, 2012, 8:15 AM > > Jay Michael wrote: > > > > > > procedure enabler( const s : string ) ; > > > procedure rejecter( const var s : string ) ; > > > > > > enabler( 'lit2' ) ; > > > rejecter( 'literal' ) ; > > > > > > > > > Why did compiling the call to > > > "enabler" first result in the compiler > > > accepting the call to "rejecter"? > > > > Plain bug: compiler got wrong internal bookkeeping and > > compiling enabler overwrote info about parameter list > > of rejecter. > > > Is this bookkeeping error fixed by the patch > you posted? Is there a separate patch you did not > post? > The patch should fix both problems. gpc uses code generator from gcc -- the part taken from gcc is usually called backend. To compile Pascal program gpc first builds appropriate data structures describing (in machine-indpendent way) code which should be generated. Layout of such data structures is defined by backend. Also backend provides several functions which create and transform data structures. To save space and usualsy also execution time backend tries to share the same data structures between parts of program. Apparently in case ouf your program backend decided that it can use the same data structure to describe properties of parameters to 'enabler' and 'rejecter'. Previous gpc code called backed function 'build_type_variant' which allows backed to re-use its input argument if there are no change and it seems that backend decided that the change done by gpc is a no-op and reused the data. The patch uses 'build_type_copy' function which disalows sharing in this case. Conseqently, this elliminates sharing of parameter description between 'enabler' and 'rejecter' and prevents overwriting. -- Waldek Hebisch hebisch(a)math.uni.wroc.pl

1 0

Re: string literal as const var parameter
by Jay Michael 09 Jul '12

09 Jul '12

procedure enabler( const s : string ) ; procedure rejecter( const var s : string ) ; enabler( 'lit2' ) ; rejecter( 'literal' ) ; Why did compiling the call to "enabler" first result in the compiler accepting the call to "rejecter"?

2 1

bug report disappeared
by Jay Michael 27 Jun '12

27 Jun '12

I submitted a bug report. It got bounced back to me, looking like I had CC'd myself. This morning, "The GPC Archives" had an entry for "June 2012", consisting of my bug report. Now, there is no entry for "June 2012", and so no sign of my bug report. Should I resubmit the bug report? Is it being processed? Has it been judged unacceptable?

2 1

rpm packages for gnu pascal now available
by trevor-b＠ovi.com 14 May '12

14 May '12

Hi for those who want to install gnu pascal on recent rpm based linux distributions, I have made rpm packages for openSuSE (various versions), fedora/centos & mandriva (most recent versions only). This is for gpc 20070904 find them on opensuse build service here ---> http://software.opensuse.org/package/gpc or go directly to my repository here ---> http://download.opensuse.org/repositories/home:/TrevorBl/ There are also subpackages for documentation, test results and a simple app wizard for kdevelop4. Test results vary a little - from 7 fails and 4 unsupported tests to zero fails & 2 unsupported (on centOS-6). (gmp-test result is unsupported for all distrubutions on open build service, but it passes fine on my system at home (OpenSuse 12.1) - does this mean I have missed some dependency in the rpm?) As always, comments and suggestions welcome. Best Regards, Trevor//

2 1

GCC 4.3.5-based GPC fails to compile under Fedora 16
by John L. Ries 22 Apr '12

22 Apr '12

I downloaded hebisch-gpc-8249f1b.tar.gz from https://github.com/hebisch/gpc and gcc-core-4.3.5.tar.bz2 from my friendly neighborhood mirror, extracted the source, created the soft links as instructed, applied the patch (gcc-4.3.5.diff) and configured as follows: ../gcc-4.3.5/configure --enable-languages=all --disable-mapped-location \ --program-suffix=435 After much compiling, I get the following: Checking multilib configuration for libgpc... mkdir -p -- x86_64-unknown-linux-gnu/libgpc Configuring in x86_64-unknown-linux-gnu/libgpc configure: WARNING: unrecognized options: --enable-multilib, --disable-mapped-location, --enable-languages, --with-target-subdir configure: creating cache ./config.cache configure: updating cache ./config.cache configure: creating ./config.status config.status: creating Makefile configure: WARNING: unrecognized options: --enable-multilib, --disable-mapped-location, --enable-languages, --with-target-subdir cat: ../../../gcc-4.3.5/libgpc/../gcc/BASE-VER: No such file or directory make[2]: Entering directory `/usr/local/src/gcc/x86_64-unknown-linux-gnu/libgpc' /usr/local/src/gcc/./gcc/xgcc -B/usr/local/src/gcc/./gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/x86_64-unknown-linux-gnu/include -isystem /usr/local/x86_64-unknown-linux-gnu/sys-include -dumpmachine > alias_file 2>/dev/null for i in `/usr/local/src/gcc/./gcc/xgcc -B/usr/local/src/gcc/./gcc/ -B/usr/local/x86_64-unknown-linux-gnu/bin/ -B/usr/local/x86_64-unknown-linux-gnu/lib/ -isystem /usr/local/x86_64-unknown-linux-gnu/include -isystem /usr/local/x86_64-unknown-linux-gnu/sys-include --print-multi-lib 2>/dev/null`; do \ dir=`echo $i | sed -e 's/;.*$//'`; \ flags=`echo $i | sed -e 's/^[^;]*;//' -e 's/@/ -/g'`; \ make CFLAGS="-O2 -g -g -O2 ${flags}" MPREFIX=${dir} build ; \ done cat: ../../../gcc-4.3.5/libgpc/../gcc/BASE-VER: No such file or directory make[3]: Entering directory `/usr/local/src/gcc/x86_64-unknown-linux-gnu/libgpc' make[3]: *** No rule to make target `../../../gcc-4.3.5/libgpc/../gcc/p/rts/Makefile.in', needed by `p/rts/Makefile'. Stop. make[3]: Leaving directory `/usr/local/src/gcc/x86_64-unknown-linux-gnu/libgpc' cat: ../../../gcc-4.3.5/libgpc/../gcc/BASE-VER: No such file or directory make[3]: Entering directory `/usr/local/src/gcc/x86_64-unknown-linux-gnu/libgpc' make[3]: *** No rule to make target `../../../gcc-4.3.5/libgpc/../gcc/p/rts/Makefile.in', needed by `32/p/rts/Makefile'. Stop. make[3]: Leaving directory `/usr/local/src/gcc/x86_64-unknown-linux-gnu/libgpc' make[2]: *** [do_multidirs] Error 2 make[2]: Leaving directory `/usr/local/src/gcc/x86_64-unknown-linux-gnu/libgpc' make[1]: *** [all-target-libgpc] Error 2 make[1]: Leaving directory `/usr/local/src/gcc' make: *** [all] Error 2 The question is, how do I proceed... or more specifically, what is BASE_VER and how do I create it? config.log is attached. --------------------------| John L. Ries | Salford Systems | Phone: (619)543-8880 x107 | or (435)867-8885 | --------------------------|

2 3

unexpected gpc command line behaviour
by trevor-b＠ovi.com 28 Feb '12

28 Feb '12

Hi, I've built gpc-20070904 for openSuSE 12.1 and the gpc command fails unless I type the full path name of gpc on the command line. For example, if I type gpc -- verbose hello.pas , gpc calls the assembler in 32 bit mode. Like this ... trevor@linux-z54m:~/projects/gpc/gpc-20070904/p/demos> gpc --verbose hello.pas Reading specs from /usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/specs Configured with: ./configure --host=x86_64-suse-linux-gnu --build=x86_64-suse-linux-gnu --enable-languages=pascal --disable-mapped-location --enable-threads=posix --disable-nls --prefix=/usr/local/gpc --infodir=/usr/local/info --mandir=/usr/local/man Thread model: posix gpc version 20070904, based on gcc-3.4.6 /usr/local/gpc/lib/gcc/x86_64-suse-linux-gnu/3.4.6/gpc1 -quiet -v hello.pas -quiet -dumpbase hello.pas -mtune=k8 -auxbase hello -famtmpfile=/tmp/ccsijV8f.gpa -version -o /tmp/cclfaLHH.s GNU Pascal version 20070904, based on gcc-3.4.6 (x86_64-suse-linux-gnu) compiled by GNU C version 3.4.6. GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 GNU Pascal Compiler PreProcessor version 20070904, based on gcc-3.4.6 as -V -Qy --32 -o /tmp/ccrX1Zh9.o /tmp/cclfaLHH.s GNU assembler version 2.21.1 (x86_64-suse-linux) using BFD version (GNU Binutils; openSUSE 12.1) 2.21.1 /tmp/cclfaLHH.s: Assembler messages: /tmp/cclfaLHH.s:10: Error: bad register name `%rbp' /tmp/cclfaLHH.s:12: Error: bad register name `%rsp' /tmp/cclfaLHH.s:15: Error: bad register name `%rip)' /tmp/cclfaLHH.s:17: Error: `movabs' is only supported in 64-bit mode /tmp/cclfaLHH.s:20: Error: bad register name `%rip)' /tmp/cclfaLHH.s:22: Error: bad register name `%rip)' ... /tmp/cclfaLHH.s:67: Error: bad register name `%rbp)' On the other hand, when I call gpc using its full path name, everything works as expected ... trevor@linux-z54m:~/projects/gpc/gpc-20070904/p/demos> /usr/local/bin/gpc --verbose hello.pas Reading specs from /usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/specs Configured with: ./configure --host=x86_64-suse-linux-gnu --build=x86_64-suse-linux-gnu --enable-languages=pascal --disable-mapped-location --enable-threads=posix --disable-nls --prefix=/usr/local/gpc --infodir=/usr/local/info --mandir=/usr/local/man Thread model: posix gpc version 20070904, based on gcc-3.4.6 /usr/local/gpc/lib/gcc/x86_64-suse-linux-gnu/3.4.6/gpc1 -quiet -v hello.pas -quiet -dumpbase hello.pas -mtune=k8 -auxbase hello -famtmpfile=/tmp/ccVD338Z.gpa -version -o /tmp/ccxCBcyY.s GNU Pascal version 20070904, based on gcc-3.4.6 (x86_64-suse-linux-gnu) compiled by GNU C version 3.4.6. GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 GNU Pascal Compiler PreProcessor version 20070904, based on gcc-3.4.6 as -V -Qy -o /tmp/ccBkjEYW.o /tmp/ccxCBcyY.s GNU assembler version 2.21.1 (x86_64-suse-linux) using BFD version (GNU Binutils; openSUSE 12.1) 2.21.1 ld --eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 /usr/lib/../lib64/crt1.o /usr/lib/../lib64/crti.o /usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/crtbegin.o -L/usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6 -L/usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/../../../../lib64 -L/usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/../../.. -L/lib/../lib64 -L/usr/lib/../lib64 /tmp/ccBkjEYW.o -lgpc -lm -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/crtend.o /usr/lib/../lib64/crtn.o trevor@linux-z54m:~/projects/gpc/gpc-20070904/p/demos> ./a.out Hello, world. trevor@linux-z54m:~/projects/gpc/gpc-20070904/p/demos> Similar (but not identical) problem when I call gpc with no arguments: When I omit the full pathname, gpc fails because it tries to link an empty file ... trevor@linux-z54m:~/projects/gpc/gpc-20070904/p/demos> gpc --verbose Reading specs from /usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/specs Configured with: ./configure --host=x86_64-suse-linux-gnu --build=x86_64-suse-linux-gnu --enable-languages=pascal --disable-mapped-location --enable-threads=posix --disable-nls --prefix=/usr/local/gpc --infodir=/usr/local/info --mandir=/usr/local/man Thread model: posix gpc version 20070904, based on gcc-3.4.6 ld --eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 /usr/lib/../lib64/crt1.o /usr/lib/../lib64/crti.o /usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/crtbegin.o -L/usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6 -L/usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/../../../../lib64 -L/usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/../../.. -L/lib/../lib64 -L/usr/lib/../lib64 --no-warn-search-mismatch -lgpc -lm -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/crtend.o /usr/lib/../lib64/crtn.o /usr/lib/../lib64/crt1.o: In function `_start': /home/abuild/rpmbuild/BUILD/glibc-2.14.1/csu/../sysdeps/x86_64/elf/start.S:109: undefined reference to `main' trevor@linux-z54m:~/projects/gpc/gpc-20070904/p/demos> With a full pathname, gpc prints some version info and exits (as expected) trevor@linux-z54m:~/projects/gpc/gpc-20070904/p/demos> /usr/local/bin/gpc --verbose Reading specs from /usr/local/gpc/lib64/gcc/x86_64-suse-linux-gnu/3.4.6/specs Configured with: ./configure --host=x86_64-suse-linux-gnu --build=x86_64-suse-linux-gnu --enable-languages=pascal --disable-mapped-location --enable-threads=posix --disable-nls --prefix=/usr/local/gpc --infodir=/usr/local/info --mandir=/usr/local/man Thread model: posix gpc version 20070904, based on gcc-3.4.6 trevor@linux-z54m:~/projects/gpc/gpc-20070904/p/demos> Note: /usr/local/bin/gpc is a link: trevor@linux-z54m:~/projects/gpc/gpc-20070904/p/demos> file /usr/local/bin/gpc /usr/local/bin/gpc: symbolic link to `/usr/local/gpc/bin/gpc' trevor@linux-z54m:~/projects/gpc/gpc-20070904/p/demos> Also, trevor@linux-z54m:~/projects/gpc/gcc-3.4.6/gcc/p/test> uname -a Linux linux-z54m 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 14:45:45 UTC 2011 (187dde0) x86_64 x86_64 x86_64 GNU/Linux trevor@linux-z54m:~/projects/gpc/gcc-3.4.6/gcc/p/test> Also, calling gpc (ie in short form, not using full pathname) from a shell script works as expected, so the test scripts work. Results copied below. I built gpc on openSuSE 11.3using the same build process (as far as I know) and there were no problems. OK, it's not a catastrophic failure, but I would like to fix it. Does anyone know what causes this, and what I need to do about it? Any ideas much appreciated. Test summary: === gpc Summary === # of tests 5111 # of expected passes 5102 # of unexpected failures 7 # of unsupported tests 2

1 1

Compile error with GNU Pascal
by Baudouin Le Charlier 28 Nov '11

28 Nov '11

Hi ! I am using a Mac OS X 10.6.8. I have downloaded GNU Pascal for Mac Os from http://www.microbizz.nl/gpc.html together with Apple’s Mac OS X assembler and linker (cctools-576) (binary). I got the following error : gp test.pas /usr/bin/ld: can't locate file for: -lcrt1.o collect2: ld returned 1 exit status I should be happy to know how to "fix" this "problem". Thanks in advance for help. Baudouin

2 3

is this a bug in GPC?
by Leo Brewin 29 Oct '11

29 Oct '11

Hi Troops, I've been using Adriaan's recent gpc (gpc436u1) on MacOSX 10.7.2 with Xcode 4.2 and I think I have found a bug. I've attached a rather odd but simple code that can produce a segmentation fault. This is what I get when running the code through gdb Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0xc0000140 0x917a4a89 in longcopy () (gdb) where #0 0x917a4a89 in longcopy () #1 0x9178ec98 in memmove$VARIANT$sse3x () #2 0x000018c0 in Jack (l1=1, u1=4, x_beg=@0xbfffed10, l2=1, u2=4, x_end=@0xbfffecf0) at foo.p:25 #3 0x00001a05 in Jill () at foo.p:48 #4 0x00001a34 in main program () at foo.p:57 #5 0x00001aab in main (argc=1, argv=0xbfffeda0, envp=0xbfffeda8) at foo.p:1 (gdb) quit It seems that the crash occurs when starting up the procedure Mary. It looks like something to do with a copy of the two arrays x_beg and x_end. If I change the formal declarations to var arrays then the problem does not occur. So I have a workaround but it is not ideal. And almost any other change to the code seems to also remove the seg fault (e.g. use just one case in the case statement, set my_choice=1, make x_beg, x_end array[1..3], add a written anywhere etc.) Any thoughts or suggestions? Cheers Leo Brewin School of Mathematical Sciences Monash University // ----------------------------------------------------------------------------------- // compile this with gpc346u1 leads to a segmentation fault // gpc -o foo foo.p program Fred(input,output); var my_choice : integer; // the segmentation fault does not ocurr if the the following two arrayas are passed as var ... procedure Mary(x_beg : array[l1..u1:integer] of double; x_end : array[l2..u2:integer] of double); begin end; procedure Jack(var x_beg : array[l1..u1:integer] of double; var x_end : array[l2..u2:integer] of double); begin case my_choice of 1: Mary(x_beg,x_end); 2: Mary(x_beg,x_end); otherwise ; end; end; procedure Jill; var x_0 : array[1..4] of double; x_1 : array[1..4] of double; begin x_0[1]:=0.0e0; x_0[2]:=0.0e0; x_0[3]:=0.0e0; x_0[4]:=0.0e0; x_1[1]:=0.1e0; x_1[2]:=0.0e0; x_1[3]:=0.0e0; x_1[4]:=0.0e0; Jack(x_0,x_1); end; begin my_choice:=1; // no problem using this my_choice:=2; // will cause a seg fault Jill; end.

1 0

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