- Gpc - gnu.de

-V and -b fail with gpc-20070904
by J. David Bryan 05 Feb '08

05 Feb '08

Attempting to use an alternate installed gpc version or gpc compiled for a different machine does not work: $ gpc -V 4.1.2 a.pas gpc: `-V' must come at the start of the command line $ gpc -b m68k a.pas gpc: `-b' must come at the start of the command line Problem appears to be that "init_gpc_options" inserts "-famtmpfile" and perhaps "-fsyntax-only" in front of all user-specified options, but "process_command" requires that "-V" and "-b" appear first. Workaround is to call the desired compiler driver directly, e.g.: $ i686-pc-mingw32-gpc-4.1.2 a.pas ...although that is somewhat awkward. Also, if the above bug is fixed, it appears that "process_command" will invoke "<machine>-gcc-<version>" instead of "<machine>-gpc-<version>". -- Dave

1 0

Re: Is it possible to use dynamic arrays in gpc?
by Waldek Hebisch 05 Feb '08

05 Feb '08

Ohonin Yuriy wrote: > I'm trying to use such a code: > > type > TVarList = object > Items:array of TVar; > count:cardinal; > ..... > end; > > In Delphi and FPC it works fine, but in GPC i get an error > > 45: warning: missing string capacity -- assuming 255 > 49: error: syntax error before `of' > > Is it possible to use dynamic arrays in gpc? gpc does not implement Delphi style dynamic arrays. As Adriaan wrote you can get very similar functionality using Extended Pascal schema and pointers. Of course Extended Pascal schema have quite different syntax. Also memory management is different: with pointers to schema you must manually deallocate arrays. -- Waldek Hebisch hebisch(a)math.uni.wroc.pl

1 0

[Fwd: GCC 4.2.3 Released]
by Adriaan van Os 04 Feb '08

04 Feb '08

-------- Original Message -------- Subject: GCC 4.2.3 Released Date: Sun, 3 Feb 2008 16:57:35 +0000 (UTC) From: Joseph S. Myers <joseph(a)codesourcery.com> Reply-To: gcc(a)gcc.gnu.org To: gcc-announce(a)gcc.gnu.org, gcc(a)gcc.gnu.org GCC 4.2.3 has been released. GCC 4.2.3 is a bug-fix release, containing fixes for regressions in GCC 4.2.2 relative to previous GCC releases. This release is available from the FTP servers listed at: http://www.gnu.org/order/ftp.html Please do not contact me directly regarding questions or comments about this release. Instead, use the resources available from http://gcc.gnu.org. As always, a vast number of people contributed to this GCC release -- far too many to thank individually!

1 0

[Patch] testsuite/gdb.pascal new testcase integer.exp
by Pierre Muller 31 Jan '08

31 Jan '08

I committed this as pascal language maintainer. For gpc mailing list mainly: I had to add to XFAIL for gpc because of the buggy line information. I used an old gpc gpc 20050331, based on gcc-3.4.4 (cygming special, gdc 0.12, using dmd 0.125) but this is the official cygwin distro of gpc. Do newer gpc binaries give better results? Pierre Muller testsuite/ChangeLog entry: 2008-01-31 Pierre Muller <muller(a)ics.u-strasbg.fr> * gdb.pascal/integers.pas: New test program. * gdb.pascal/integers.exp: New testcase. Index: gdb.pascal/integers.pas =================================================================== RCS file: gdb.pascal/integers.pas diff -N gdb.pascal/integers.pas --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ gdb.pascal/integers.pas 31 Jan 2008 14:49:23 -0000 1.1 @@ -0,0 +1,51 @@ +{ + Copyright 2008 Free Software Foundation, Inc. + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 3 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program. If not, see <http://www.gnu.org/licenses/>. +} + +program integers; + + +function add(a,b : integer) : integer; +begin + add:=a+b; +end; + +function sub(a,b : integer) : integer; +begin + sub:=a-b; +end; + +var + i, j, k, l : integer; + +begin + i := 0; + j := 0; + k := 0; + l := 0; { set breakpoint 1 here } + i := 1; + j := 2; + k := 3; + l := k; + + i := j + k; + + j := 0; { set breakpoint 2 here } + k := 0; + l := add(i,j); + l := sub(i,j); + +end. Index: gdb.pascal/integers.exp =================================================================== RCS file: gdb.pascal/integers.exp diff -N gdb.pascal/integers.exp --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ gdb.pascal/integers.exp 31 Jan 2008 14:49:23 -0000 1.1 @@ -0,0 +1,129 @@ +# Copyright 2008 Free Software Foundation, Inc. +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 3 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see <http://www.gnu.org/licenses/>. + +if $tracelevel then { + strace $tracelevel +} + +load_lib "pascal.exp" + +set testfile "integers" +set srcfile ${testfile}.pas +set binfile ${objdir}/${subdir}/${testfile}$EXEEXT + +if {[gdb_compile_pascal "${srcdir}/${subdir}/${srcfile}" "${binfile}" executabl e [list debug ]] != "" } { + return -1 +} + +gdb_exit +gdb_start +gdb_reinitialize_dir $srcdir/$subdir +gdb_load ${binfile} +set bp_location1 [gdb_get_line_number "set breakpoint 1 here"] +set bp_location2 [gdb_get_line_number "set breakpoint 2 here"] + +if { [gdb_breakpoint ${srcfile}:${bp_location1}] } { + pass "setting breakpoint 1" +} +if { [gdb_breakpoint ${srcfile}:${bp_location2}] } { + pass "setting breakpoint 2" +} + +# Verify that "start" lands inside the right procedure. +if { [gdb_start_cmd] < 0 } { + untested start + return -1 +} + +gdb_test "" ".* at .*${srcfile}.*" "start" + +gdb_test "cont" "Breakpoint .*:${bp_location1}.*" "Going to first breakpoint" + +gdb_test "print i" ".* = 0" "Print i before assigned to 1" + +gdb_test "next" "i := 1;" "Next to 'i := 1' line" +gdb_test "next" "j := 2;" "Next to 'j := 2' line" +# At that point, +# i should be equal to 1 +gdb_test "print i" " = 1" +# but j should still be equal to zero +if { $pascal_compiler_is_gpc } { + setup_xfail *-*-* +} +gdb_test "print j" " = 0" "Test j value before assignment" + +gdb_test "next" "k := 3;" "Next to 'k := 3' line" +gdb_test "next" "l := k;" "Next to 'l := k' line" + +#j should be equal to 2 +gdb_test "print j" " = 2" +# k should be equal to 3 +gdb_test "print k" " = 3" +# But l shoud still be zero +if { $pascal_compiler_is_gpc } { + setup_xfail *-*-* +} +gdb_test "print l" " = 0" + +# Test addition +gdb_test "print i + j" " = 3" +gdb_test "print i + k" " = 4" +gdb_test "print j + k" " = 5" +gdb_test "print i + j + k" " = 6" + +# Test substraction +gdb_test "print j - i" " = 1" +gdb_test "print i - j" "= -1" +gdb_test "print k -i -j" " = 0" +gdb_test "print k -(i + j)" " = 0" + +# Test unany minus +gdb_test "print -i" " = -1" +gdb_test "print (-i)" " = -1" +gdb_test "print -(i)" " = -1" +gdb_test "print -(i+j)" " = -3" + +# Test boolean operators =, <>, <, <=, > and >= +gdb_test "print i + 1 = j" " = true" +gdb_test "print i + 1 <> j" " = false" +gdb_test "print i + 1 < j" " = false" +gdb_test "print i + 1 <= j" " = true" +gdb_test "print i + 1 > j" " = false" +gdb_test "print i + 1 >= j" " = true" + +# Test multiplication +gdb_test "print 2 * i" " = 2" +gdb_test "print j * k" " = 6" +gdb_test "print 3000*i" " = 3000" + +#Test div and mod operators +gdb_test "print 35 div 2" " = 17" +gdb_test "print 35 mod 2" " = 1" + +# Test several operators together +gdb_test "print i+10*j+100*k" " = 321" +gdb_test " print (i + 5) * (j + 7)" " = 54" + +# 'set i' does not work, as there are set sub-commands starting with 'i' +# Thus we need to use 'set var i' +gdb_test "set var i := 2" " := 2" +gdb_test "print i" " = 2" "Testing new i value" + +gdb_test "cont" \ + "Breakpoint .*:${bp_location2}.*" \ + "Going to second breakpoint" +gdb_test "print i" \ + ".* = 5.*" \ + "Value of i after assignment"

1 0

Help installing on Mac OSX 10.5
by Tom Schneider 30 Jan '08

30 Jan '08

Could someone point me to simple step-by-step instructions for complete installation of GPC on Mac OSX 10.5? I got: http://www.microbizz.nl/gpc.html GNU Pascal 3.4.5u2 installer for Mach-O Intel (Intel native and PowerPC cross compiler) (16.6 MB) and was able to get it installed at: /Developer/Pascal/gpc345u2/bin/gpc so: [toot:~/now/delila] tds% which gpc /usr/bin/gpc [toot:~/now/delila] tds% dir /usr/bin/gpc lrwxr-xr-x 1 root wheel 34 Jan 29 23:19 /usr/bin/gpc@ -> /Developer/Pascal/gpc3 45u2/bin/gpc but when I try to compile I get: /usr/bin/ld: can't locate file for: -lcrt1.o (along with various warnings about my program that are ok.) I get no compiled result. (I also installed the Mac OS X Pascal Interfaces but that did not help.) Adding: --unit-path=/Developer/Pascal/GPCPInterfaces -I/Developer/Pascal/GPCPInterfaces to my control script did not help. I have no clue as how to fix this. Thanks, Tom Dr. Thomas D. Schneider National Institutes of Health National Cancer Institute Center for Cancer Research Nanobiology Program Molecular Information Theory Group Frederick, Maryland 21702-1201 toms(a)ncifcrf.gov permanent email: toms(a)alum.mit.edu http://www.ccrnp.ncifcrf.gov/~toms/

2 1

Problem porting to Mac OS-X
by Martin Liddle 16 Jan '08

16 Jan '08

Apologies because this is probably a silly question. I have a small application that I have written in Gnu Pascal that works nicely under Fedora Core 7 on an Intel PC using gpc 20020502 (yes I know it is old but there are reasons not connected with this task). I now want to port the application to Apple Macs running OS-X. I have downloaded and installed gpc 20051116 from <http://www.microbizz.nl/gpc.html> and that appears to be working. My application compiles OK but fails at the linking stage with the message: /usr/bin/ld: can't locate file for : -lcrt1.o The only unit my application includes is gpc.pas and the only screen input and output is simple reads and writes. A search doesn't find a crt1.o anywhere on the system. What do I do next? -- Martin Liddle, Tynemouth Computer Services, 3 Kentmere Way, Staveley, Chesterfield, Derbyshire, S43 3TW. Web site: <http://www.tynecomp.co.uk>.

3 9

bug report
by Russell Whitaker 04 Jan '08

04 Jan '08

hi given: program bug; procedure foo; begin end; begin foo( 1 ); writeln("OK"); end. gives these compile errors: bug.pas: In main program: bug.pas:8: error: too many (>1) arguments to routine `foo' bug.pas:3: error: routine declaration bug.pas:8: error: too few (1) arguments to function `foo' russ

1 0

Assignment of cstrings passed to C routine
by Harmonious Botch 25 Dec '07

25 Dec '07

I'm trying to call a C routine from a pascal program, and pass string data back and forth. I can call it, I can pass integers back and forth ( thanks to Frank H ), but I can't pass strings. Attempts to assign data to a cstring either result in segmentation errors or garbage in the string. The following is the C routine: #include <stdio.h> char c_str[13]; void c_print_str() { printf ("Now in C routine called from Pascal code.\n"); printf ("string is %s.\n", c_str); fflush (stdout); /* So the text really appears now. */ } The following is the pascal program: program str_trans(input); (* This is an attempt to pass a string from a pascal program to a c function. The corresponding c code is in str_trans.c It is compiled with gpc --automake --unit-path=/home/x/pas str_trans.pas -o str_trans *) {$L str_trans.c} {$X+} procedure c_print_str; asmname 'c_print_str'; var char_ptr: ^char; c_str: cstring; asmname 'c_str'; external; begin new( char_ptr ); char_ptr^ := 'x'; writeln( char_ptr^ ); flush( output ); c_str := char_ptr; writeln( 'calling c function' ); c_print_str; end. As shown, it ends up with garbage in c_str. If I change the value of char_ptr^, the garbage changes. If I try simple assignment in the pascal program, such as c_str := 'x'; or c_str[3] := 'x'; or c_str^ := char_ptr^ it compiles ok, but generates run-time segmentation errors. So, the ideal help would be if someone could explain to me how to assign to c_str. If not, does anyone know how to pass string data between C and Pascal programs in some other manner? Thanks, and happy solstace to all! HB -- View this message in context: http://www.nabble.com/Assignment-of-cstrings-passed-to-C-routine-tp14472794… Sent from the Gpc mailing list archive at Nabble.com.

4 6

Memory layout of array of variable size.
by Bastiaan Veelo 24 Dec '07

24 Dec '07

Hi, In an attempt to hook up to GTK+, I am trying to pass a Pascal array of varible size to C. Static arrays are fine, but these arrays carry some additional information like capacity and size, and I gues they could be received as a struct on the C-side. However, I cannot figure out the structure that the struc should have. I do like this in Pascal: procedure YGTK_init(var argc : CInteger; argv : array of CString); external name 'YGTK_init'; procedure Y_init; var argc : CInteger; argv : array[0..ParamCount] of CString; Counter : integer; begin argc := ParamCount+1; for Counter := 0 to ParamCount do begin argv[Counter] := NewCString(ParamStr(Counter)); end; YGTK_init(argc, argv); end; And like this in C: struct t_argv { int end; void *argv; }; void YGTK_init( int *argc, struct t_argv argv ) { printf("In ygtk.c:YGTK_init.\n"); printf("argv.end: %d\n", argv2.argc); printf("argv.argv address: %p\n", argv2.argv); printf("argv.argv int: %d\n", argv2.argv); printf("argv.argv string: %s\n", argv2.argv); printf("number of arguments: %d\n", *argc); } So I figured out that the first element in the struct is an integer containing the length-1 of the array, but what it should look like for the rest I do not know yet. Do you have an idea? Thanks, Bastiaan.

5 9

Re: dispose: bug or feature?
by Scott Moore 13 Dec '07

13 Dec '07

Scott Moore wrote: >> From: Russell Whitaker <russ(a)ashlandhome.net> >>> >>> On Mon, 10 Dec 2007, Scott Moore wrote: >>> >>> [..] >>>> What did you expect to happen? >>>> >>> I expected "dispose" to undo what "new" does. >>> Could not find a comment in gpc's source that states otherwise. >>> >>> At present, >>> >>> new(p) >>> 1. allocates a block of memory from the heap, the size is the size >>> that p wants to point to. >>> 2. returns the address of that memory block. >>> >>> dispose(p) >>> 1. marks the block of memory that p points to as free. >>> (I say "marks" because the block doesn't disapear) >>> >>> Thus, this works, but shouldn't: >>> >>> writeln( p^ ); >>> dispose( p ); >>> writeln( p^ ); >> >> ============================================= >> 6.5.4 Identified-variables >> An identified-variable shall denote the variable, if any, identified >> by the value of the pointer-variable >> of the identified-variable (see 6 .4 .4 and 6 .6 .5 .3) shall be >> accessible until the termination of the >> activation of the program-block or until the variable is made >> inaccessible (see the required procedure >> 28 >> ISO/IEC 7185 :1990(E) >> dispose, 6.6 .5 .3). >> NOTE | The accessibility of the variable also depends on the existence >> of a pointer-variable that has >> attributed to it the corresponding identifying-value. >> A pointer-variable shall be a variable-access that denotes a variable >> possessing a pointer-type . It shall >> be an error if the pointer-variable of an identified-variable either >> denotes a nil-value or is undefined. >> It shall be an error to remove from the set of values of the >> pointer-type the identifying-value of an >> identified-variable (see 6 .6 .5 .3) when a reference to the >> identified-variable exists. >> Examples: >> p1fi >> p1f .fatherf >> p1's .sibling's .father's >> 6.5 >> =========================================================== >> The statement "writeln( p^ );" after dispose is an "error", dispose >> left p undefined. >> >>> If you dig into gpc's heap.pas you will find code that is the >>> equivalent of: >>> >>> if p <> nil then >>> dispose(p); >>> >>> What I'd like to see is the equivalent of: >>> >>> if p <> nil then >>> begin >>> dispose(p); >>> p := nil; >>> end >>> else >>> writeln( stderr,"WARN: illegal use of dispose"); >>> >>> In places the specs are hard to follow, but I think the specs would >>> allow this. >>> >>> Russ >>> >> >> ====================================================== >> 6.6 .5.3 Dynamic allocation procedures >> >> ... >> >> dispose(q) >> >> shall remove the identifying-value denoted by the expression q from >> the pointer-type of q . It >> shall be an error if the identifying-value had been created using the >> form new(p,c l , . . .,cn). >> >> dispose(q,kl , . . .,km) >> >> shall remove the identifying-value denoted by the expression q from >> the pointer-type of q . The >> case-constants k 1, . . .,km shall be listed in order of increasing >> nesting of the variant-parts . It >> shall be an error unless the variable had been created using the form >> new(p,c 1 , . . .,cn ) and m is >> equal to n . It shall be an error if the variants in the variable >> identified by the pointer value of >> q are different from those specified by the values denoted by the >> case-constants k 1, . . .,km. >> >> NOTE | The removal of an identifying-value from the pointer-type to >> which it belongs renders the identifiedvariable >> inaccessible (see 6 .5.4) and makes undefined all variables and >> functions that have that value >> attributed (see 6 .6 .3 .2 and 6 .8 .2 .2). >> >> It shall be an error if q has a nil-value or is undefined. >> =================================================== >> >> So, again, it is an error (to pass nil to dispose). However, the >> standard leaves it up to the >> implementation when and if such errors are detected, so this is a >> "quality" issue: >> >> ================================================= >> 3.1 Error >> A violation by a program of the requirements of this International >> Standard that a processor is >> permitted to leave undetected. >> ================================================== >> >> I'll bet a nickel that the dispose nil behavior you saw was designed >> to compensate >> for disposals of zero length data. I had to solve that problem, but >> did it using a key address, >> i.e., new() returns a specific, predefined location that is the >> universal zero length pointer. >> >> Scott Moore >> > >

3 2