- Gpc - gnu.de

Question about -Widentifier-case
by Peter Schorn 24 Jan '06

24 Jan '06

I have a question on the meaning of the identifier-case warning in gpc (gpc345u2 on Mac OS 10.4.4). Compiling the program below I get three warnings but I'd expect none since in all three cases the two referenced variables are different. Is my expectation wrong? Best regards, Peter { 1} program cap; { 2} { compile with gpc -o cap -Widentifier-case cap.pas } { 3} { 4} procedure p(A: integer); { 5} { 6} procedure q(a: integer); { cap.pas:6: warning: capitalisation of identifier `a' doesn't match } { 8} { cap.pas:4: warning: previous capitalisation `A' } { 9} begin {10} a := 1; {11} end; {12} {13} begin { p } {14} A := 0; { cap.pas:14: warning: capitalisation of identifier `A' doesn't match } {16} { cap.pas:6: warning: previous capitalisation `a' } {17} end; {18} {19} procedure r(a: integer); { cap.pas:19: warning: capitalisation of identifier `a' doesn't match } {21} { cap.pas:14: warning: previous capitalisation `A' } {22} begin {23} a := 1; {24} end; {25} {26} begin {27} end.

3 2

Creating Universal static library called from XCode 2.2.1 Carbon Application
by Glenn Howes 23 Jan '06

23 Jan '06

I have a legacy static library written in Pascal which I need to call from a C++ application targeting both PowerPC and x86 processors on the Mac OS X platform ( a so-called universal binary). After compiling and linking everything together, I'm having trouble calling the Pascal runtime libraries: i.e. I crash. Software used: glenn% gpc -v Reading specs from /Developer/Pascal/gpc345u2/lib/gcc/powerpc-apple- darwin8/3.4.5/specs Configured with: ../gcc-3.4.5/configure --enable-languages=pascal,c -- enable-threads=posix --target=powerpc-apple-darwin8 --host=powerpc- apple-darwin8 --build=powerpc-apple-darwin8 --prefix=/Developer/ Pascal/gpc345u2 Thread model: posix gpc version 20051116, based on gcc-3.4.5 gpc-i386 -vReading specs from /Developer/Pascal/gpc345u2/lib/gcc/i386- apple-darwin8/3.4.5/specs Configured with: ../gcc-3.4.5/configure --enable-languages=pascal,c -- enable-threads=posix --target=i386-apple-darwin8 --host=powerpc-apple- darwin8 --build=powerpc-apple-darwin8 --prefix=/Developer/Pascal/ gpc345u2 --with-sysroot=/Developer/SDKs/MacOSX10.4u.sdk/ --with- arch=pentium-m --with-tune=prescott Thread model: posix gpc version 20051116, based on gcc-3.4.5 Mac OS X 10.4.4 XCode 2.2.1 Source: 34 files of legacy Pascal which I've gone through and fixed all of the compiler errorss and most of the warnings. Steps I've taken. 1) Compiled and packaged using gpc, libtool, and lipo: gpc -c --automake -Wl,-framework,Carbon -funit-path=/Developer/Pascal/ GPCPInterfaces/ MySrc.p libtool -static *.o -o MyLibPPC.a rm *.gpi rm *.o gpc-i386 -c --automake -Wl,-framework,Carbon -funit-path=/Developer/ Pascal/GPCPInterfaces/ MySrc.p libtool -static *.o -o MyLibx86.a lipo *.a -create -output MyLib.a 2) Made a universal version of the gpc.a library lipo /Developer/Pascal/gpc345u2/lib/gcc/i386-apple-darwin8/3.4.5/ libgpc.a /Developer/Pascal/gpc345u2/lib/gcc/powerpc-apple- darwin8/3.4.5/libgpc.a -create -output gpc.a 3) Added both libraries to my XCode 2.2.1 C++ application 4) Compile and Links without running, crashes as soon as it tries to call WriteLn, if I remove the WriteLn, it crashes later in a call to the file routine Assign, which might be the first runtime library call. I declare the entry in C++ as: extern "C" short MyEntry(const char *path); In Pascal, I declare it as const MaxPointerChars = 20000; Type PAPointerChar=^APointerChar; APointerChar = Packed Array [0..MaxPointerChars] of Char; Int16 = Integer attribute ( size = 16); ... function MyEntry(DllPathC:PAPointerChar):Int16; attribute (name = 'MyEntry'); ... function MyEntry(aCString:PAPointerChar):Int16; var DLLPath:String2048; pathLength:Int32; i:Int32; begin pathLength := StrLen(aCString); if pathLength > 2048 then pathLength := 2048; DLLPath := ''; for i := 1 to pathLength do begin DLLPath := DLLPath + aCString^[i-1]; end; WriteLn(DLLPath); { crashes here} ... gdb gives me the following console output: Running… Program received signal: "EXC_BAD_ACCESS". Unable to disassemble _p_Write_Init. 5) I've written a little test application in Pascal to debug the libraries code (when it is not packaged as a library but compiled directly into the application) and the code works perfectly well in that environment. The debugging was done with XCode 2.1 as I believe there is a problem with gpc and XCode 2.2. So how do I fix this?

2 4

GPC 20051116 on Sparc Solaris
by Pascal Viandier 22 Jan '06

22 Jan '06

I ran the test suite against gpc 20051116 on SUN Sparc Solaris with the following results: Test Run By pascal on 2006-01-16 13:41:36 Native configuration is sparc-sun-solaris2.6 (perfdev) === gpc tests === Running target any Running testsuite ... UNSUPPORTED: agettext2test.pas UNSUPPORTED: aregextest.pas UNSUPPORTED: asmtest.pas UNSUPPORTED: crttest.pas UNSUPPORTED: fjf165a.pas FAIL: fjf980a.pas FAIL: fjf980b.pas UNSUPPORTED: gmptest.pas UNSUPPORTED: longr2.pas === gpc Summary === # of tests 4969 # of expected passes 4960 # of unexpected failures 2 # of unsupported tests 7 gpc version 20051116, based on gcc-3.4.4 In the two failing tests there is a "packed array [1 .. 1] of Boolean". If I run the tests by hand I get bus error. If I remove the "packed" in the array declaration, both tests work as expected. Is this a Sparc Solaris - specific bug? Regards Pascal Viandier pascal(a)accovia.com

2 1

Program parameters with ISO 7185
by Brian Wichmann 20 Jan '06

20 Jan '06

I was a co-author of an algorithm written in Pascal (ISO 7185) which read: PROGRAM stvpas(datafile, output); {This program counts the votes in a Single Transferable Vote election, using Meek's method, and reports the results} ... The datafile was reread on every iteration of the algorithm. Am I correct in stating that that the program cannot be run with gpc without making a change to the program to assign datafile to an external file? Brian.

3 5

Changing access:
by CBFalconer 20 Jan '06

20 Jan '06

Darned if I know how to set this up. Please change my access so that mail is delivered to: cbfalconer(a)maineline.net and accepted from there and worldnet.att.net, att.net, or yahoo.com (all user cbfalconer). I would still like a reply-to gpc... to appear in the list messages sent to me. -- "If you want to post a followup via groups.google.com, don't use the broken "Reply" link at the bottom of the article. Click on "show options" at the top of the article, then click on the "Reply" at the bottom of the article headers." - Keith Thompson More details at: <http://cfaj.freeshell.org/google/>

1 0

Re: Dynamic arrays dimensions
by Silvio a Beccara 20 Jan '06

20 Jan '06

> This version doesn't do any range checking. This means the code may > have worked incorrectly, unnoticed. Too bad... anyway now I'm using the latest one. > Are you using a 64 bit platform? This array would have a size of > 6.4 GB which is not possible on 32 bit. From your question I understand that the maximum limit coincides with the physical memory (which is limited to 4 GB on a 32-bit machine). I'm using a 32 bit machine, so I adjusted the dimensioning of that array (and the size of the calculation) to fit my memory. Thanks Silvio a Beccara -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Trova la tua anima gemella con Meetic. Iscriviti subito gratis: potrai trovare migliaia di single in linea e chattare con loro! Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid@48&d-1

3 2

Re: GPC on i686-apple-darwin
by Waldek Hebisch 19 Jan '06

19 Jan '06

Adriaan van Os wrote: > You were quite right about -fPIC. All the failures, except emil9.pas > disappear with -fno-pic. However, many of the other tests fail with > -fno-pic, because the option disables dynamic linking on Mac OS X. The > PPC back-end has a workaround (-mdynamic-no-pic) but that doesn't seem > to work for i686-apple-darwin. > I have just realized that Darwin PIC problem have nothing to do with Linux PIC problems: Darwin does not use the binutils feature (ELF GOT relocations) that Linux uses. > Updating the linker and assembler to odcctools-20050327 had no effect > on testsuite results. > > So, I must either > - find a backport of i686-apple-darwin PIC fixes > - find a solution for gcc-3.4 bootstrap problems > - wait for gcc-4.0 support. > > Still, I am glad with the results so far. > Well, I was able build 3.3.6 based cross-compiler for i686-apple-darwin target, and I can see duplicate labels in the assembler output. It seems that 3.4.3 has changed the parts responsible for generating those labels. I have found that 3.4.[34] contain blatant bug with easy fix: --- gcc-3.4.4/gcc/config/i386/darwin.h.orig Thu Jun 16 01:10:29 2005 +++ gcc-3.4.4/gcc/config/i386/darwin.h Thu Jun 16 01:10:32 2005 @@ -43,7 +43,7 @@ /* Use the following macro for any Darwin/x86-specific command-line option translation. */ -#define SUBTARGET_OPTION_TRANSLATE_TABLE +#define SUBTARGET_OPTION_TRANSLATE_TABLE { 0, 0 } #define ASM_SPEC "-arch i386 \ %{Zforce_cpusubtype_ALL:-force_cpusubtype_ALL} \ After that I can build the compiler proper. However I get ICE when building gcc runtime. Trying gpc on knuth3.pas (to get assembler output) give me ICE. Both ICE-s seem related to generting labels needed in PIC code... So, it seems that nobody tried gcc-3.4.x for i686-darwin for almost a year (ChangeLog entry for SUBTARGET_OPTION_TRANSLATE_TABLE change is from 2004-08-23) -- Waldek Hebisch hebisch(a)math.uni.wroc.pl

2 9

Pascal calling Ada (works)
by lanceboyle＠qwest.net 19 Jan '06

19 Jan '06

(This post is related to two earlier posts by me, "Linking Ada to Pascal" and 'Where is documentation for "new argument to _p_initialize (@)" PCStrings.') I've had some success here. The following two files (Pascal main program) and compile commands work. <file pascalcallsada.pas> program pascalcallsada (input, output); procedure youradapackagesubroutine; external name 'myadapackagesubroutine'; procedure adainit; external name 'adainit'; procedure adafinal; external name 'adafinal'; begin adainit; writeln('Hello from pascalcallsada.'); youradapackagesubroutine; writeln('Goodbye from Pascal main program.'); adafinal; end. <file myadapackage.ads> package myadapackage is procedure myadapackagesubroutine; pragma Export(Convention => C, Entity => myadapackagesubroutine, External_Name => "myadapackagesubroutine"); end myadapackage; <file myadapackage.adb> with Ada.Text_IO; use Ada.Text_IO; package body myadapackage is procedure myadapackagesubroutine is begin Put_Line("Hello from myadapackagesubroutine."); end myadapackagesubroutine; begin Put_Line("Initializing myadapackage."); end myadapackage; <Compile commands> gpc -c pascalcallsada.pas gnatmake -c myadapackage.adb gnatmake -c myadaprogram.adb gnatbind -n myadapackage.ali myadaprogram.ali gnatlink myadaprogram.ali pascalcallsada.o `gpc -print-file- name=libgpc.a` \ -o mypascalprogram <Out from running> Initializing myadapackage. Hello from pascalcallsada. Hello from myadapackagesubroutine. Goodbye from Pascal main program. Jerry

2 3

Crash with sets under Solaris
by Pascal Viandier 16 Jan '06

16 Jan '06

Hi all, I am sorry to be back on this subject after a so long time, but I just hit the problem with a real-life program. I applied the patch you suggested and ran the gpc test suite again. It gives worse results than previously with 97 unexpected failures. If I run some programs under gdb I get Segmentation faults in various places in sets.pas. For example SetCopy (line 286) adam3g adam3h assumptions awindte2 awindtes dostest SetEqual (line 215) adam3k adam3l adam3m adam3n WordNumber (line 113) adam3q adam3r ancestor2 Test fail with no core dump az44 chief41 couper10 couper8 gpc gives: warning: `absolute' declaration increases required alignment and test fail chris4 chris5 Is there a patch to solve this problem? If you need more information, I will do my best to give it. Regards Pascal Viandier pascal(a)accovia.com -----Message d'origine----- De : gpc-owner(a)gnu.de [mailto:gpc-owner@gnu.de] De la part de Waldek Hebisch Envoyé : May 25, 2005 16:33 À : gpc(a)gnu.de Objet : Re: RE : bigsetdemo strange result Pascal Viandier wrote: > Hi, > > At your suggestion, I ran the gpc test suite. > Here is the summary result: > > Test Run By pascal on 2005-05-25 10:45:41 > Native configuration is sparc-sun-solaris2.6 (perfdev) > gpc 20050331, based on gcc-3.4.3, flags: -g -O3 -W -Wall -Wno-unused > > Nuber of tests: 4947 > Number of Ok: 4828 > Number of tests skipped: 7 > Number of failures: 56 (includes internal compiler error and some > coredumps) > Number of coredumps: 47 > Number of compiler errors: 2 > > > Should I worry? > Something is really broken. At first glance all failures involve sets, so it may be just a single problem. -- Waldek Hebisch hebisch(a)math.uni.wroc.pl

2 6

Re: Dynamic arrays dimensions
by Maurice Lombardi 16 Jan '06

16 Jan '06

Silvio a Beccara a écrit: > I think you are right, I calculated the size, too and it is actually more than > my physical memory. Is the maximum heap space as big as the physical RAM, or > it is less? It depends on your system, linux mingw djgpp or other. I use DJGPP (dos based). There it can be somewhat higher, by using virtual memory obtained by swapping to disk. But this is at the expense of a considerable slow-down of the programs, so usually I make every effort _not_ to use this "facility". Maurice -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 63 54 95 mailto:Maurice.Lombardi@ujf-grenoble.fr

1 0