Gpc

gpc@gnu.de

5400 discussions

Start a nNew thread

lgcc?
by Paul Daily 10 Feb '03

10 Feb '03

2 1

Re: GPC: daily digest V1 #206
by Tom Schneider 10 Feb '03

10 Feb '03

I noticed a minor error in the GPC list: > GPC: daily digest > > This is Digest Volume 1 : Issue 206 : 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. Re: use of 'in' clause > Re: Inefficiency of `mod' > gpc-20030209 > lgcc? > Re: gpc-20030209 > > ---------------------------------------------------------------------- > > Date: Sun, 9 Feb 2003 13:35:08 +0100 > From: Frank Heckenbach <frank(a)g-n-u.de> > To: gpc(a)gnu.de > Subject: Re: use of 'in' clause > Message-ID: <200302091235.NAA09482(a)goedel.fjf.gnu.de> ... The first message is: > Subject: Re: use of 'in' clause But in the 'index' that line is fused with the previous line: > and who posted it, followed by the full text of all messages. Re: use of 'in' clause I suggest putting two additional carriage returns (writeln(digest);writeln(digest);) before the first message index line. This will separate it away from the introductory paragraph. Tom Dr. Thomas D. Schneider National Cancer Institute Laboratory of Experimental and Computational Biology Frederick, Maryland 21702-1201 toms(a)ncifcrf.gov permanent email: toms(a)alum.mit.edu (use only if first address fails) http://www.lecb.ncifcrf.gov/~toms/

1 0

Optimisation crashes
by Silvio a Beccara 09 Feb '03

09 Feb '03

Hi, when compiling a program with optimisation option -O3 sometimes everything works fine, some others the program crashes for no reason. Recompiling without -O3 eliminates the problem. I use GPC version: Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/specs gpc version 20020304, based on 2.95.3 20010315 (release) Any suggestion? Silvio a Beccara

3 5

Compiler crash
by Andrew Gregory 07 Feb '03

07 Feb '03

I'm getting an access violation in gpc1.exe at 0x00578a24 during compile on Windows NT. I'm using MinGW 2.0.0-3 with core gcc 3.2.1, and gpc 2.1 20020510 (from MinGW site). The code is in the form of an include file. I tested it as a console application - and it works. I've re-packaged so that it can be called from C, based on the gpc_c_pas.pas example. Two integer functions are called, with all parameters being passed as double value and variable parameters. Now I get a crash. Someone may have seen this crash before - any ideas? Dr Watson produced this: function: <nosymbols> 005789fb 0f84c7000000 je 00578ac8 00578a01 8b5e10 mov ebx,[esi+0x10] ds:02034226=???????? 00578a04 85db test ebx,ebx 00578a06 751c jnz 00578a24 00578a08 681a090000 push 0x91a 00578a0d 68d2895700 push 0x5789d2 00578a12 68a04a5700 push 0x574aa0 00578a17 68fb815700 push 0x5781fb 00578a1c e87bc30600 call 005e4d9c 00578a21 8d7600 lea esi,[esi] ds:02034226=???????? FAULT ->00578a24 f6430a80 test byte ptr [ebx+0xa],0x80 ds:0267a08e=?? 00578a28 0f848e000000 je 00578abc 00578a2e 837b1000 cmp dword ptr [ebx+0x10],0x0 ds:0267a08e=???????? 00578a32 7413 jz 00578a47 00578a34 833ddca65e0000 cmp dword ptr [005ea6dc],0x0 ds:005ea6dc=00000000 00578a3b 743f jz 00578a7c 00578a3d a1d8a65e00 mov eax,[005ea6d8] ds:005ea6d8=00a35790 00578a42 394338 cmp [ebx+0x38],eax ds:0267a08e=???????? 00578a45 7535 jnz 00578a7c 00578a47 83c4f8 add esp,0xf8 00578a4a 6820855700 push 0x578520 00578a4f 53 push ebx Andrew. ------------------------------------------------------------------- This e-mail and any attachments may contain confidential and/or privileged material; it is for the intended addressee(s) only. If you are not a named addressee, you must not use, retain or disclose such information. NPL Management Ltd cannot guarantee that the e-mail or any attachments are free from viruses. NPL Management Ltd. Registered in England and Wales. No: 2937881 Registered Office: Teddington, Middlesex, United Kingdom TW11 0LW. -------------------------------------------------------------------

3 2

Re: Porting from DEC pascal to GPC
by Wood David 07 Feb '03

07 Feb '03

Rob Koopman wrote: We are investigating to port about 400.000 lines of DEC Vax Pascal (started as VMS application later ported to OSF1 UNIX). One of our concerns is the maturity of the GPC environment. During our initial tests we encountered some compiler problems (segfault, internal error). An obvious question is did someone else try this before. ( DEC Pascal has funny extentions) We've ported quite a lot of DEC Pascal to GPC without major problems. Certainly GPC2.1 hasn't given us problems with segfaults or internal errors on both i386 or Alpha platforms. We have had to do quite a lot of manual code conversions though. Areas which spring to mind that needed changing in our code was: GPC doesn't read enumerated types from files; GPC doesn't support the :=ZERO assignment; GPC doesn't use file i/o and read qualifiers, especially ERROR:= CONTINUE; VARYING [] OF CHAR must be replaced by STRING(); REAL is best defined as SINGLE; VMS runtime library functions aren't available (obviously!). I can't do key detection as I do under VMS INHERIT and ENVIRONMENT become INTERFACE/IMPLEMENTATION and USES Remove [GLOBAL] and [EXTERNAL] [STATIC] becomes static No D+0 etc. for double precision exponents The only compiler bug - global string definitions in modules don't always work yet (I don't think?) I have code examples of how I've worked around the enumerated type reading and ZERO issues if you wish. 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.

3 2

UCSD strings
by Adriaan van Os 07 Feb '03

07 Feb '03

In the GPC docs I found that UCSD (BP) strings are on the todo list for the compiler. Below is an outline for an intermediate solution I write for the Macintosh Toolbox. The "Carbon" API has 700 (!) references to UCSD-Pascal strings. For binary compatibility, I have little choice. If appropriate, I will be pleased to write runtime support routines (in Pascal) for UCSD strings, when they are getting integrated into the compiler. Regards, Adriaan van Os ----------------- TYPE Str255 = PACKED RECORD Length: byte; chars: packed array[ 1..255] of char END; Str32 = PACKED RECORD Length: byte; chars: packed array[ 1..32] of char; pad: char {for binary compatibility} END; {etcetera} OPERATOR + ( const theStr1 : Str255; const theStr2 : Str255) AD: Str255; OPERATOR = ( const theStr1 : Str255; const theStr2 : Str255) EQ: Str255; OPERATOR > ( const theStr1 : Str255; const theStr2 : Str255) GT: Str255; OPERATOR < ( const theStr1 : Str255; const theStr2 : Str255) ST: Str255; OPERATOR >= ( const theStr1 : Str255; const theStr2 : Str255) GE: Str255; OPERATOR <= ( const theStr1 : Str255; const theStr2 : Str255) SE: Str255; Plus: (1) standard routines Pos, Insert, Delete and Concat (2) conversion routines from and to string-constants and GPC "long strings".

2 1

gcc-3.2.2
by Russell Whitaker 06 Feb '03

06 Feb '03

Hi gcc-3.2.2 is now out. Tried building gpc with it: Minor problem: Patch for 3.2.1 works, gives a few offset complaints. Not so minor problem: Build quit - incompatable definitions of global_trees p/gpc.h: 667 tree.h: 1951 Hope this helps Russ

2 2

Re: Porting from DEC pascal to GPC
by Wood David 06 Feb '03

06 Feb '03

> Some general pointers beyond those I already mentioned: > > Define a few syntax reassignments at the top of the DEC Pascal: > > {--- Command Substitution ---} > > {$define WRITEV WRITESTR} > {$define READV READSTR} > > {--- Type Substitution ---} > > {$define uint cardinal} > {$define sngl single} > {$define dble double} > {$define zero(a) DEC_zero(a, #0, sizeof(a))} > > {--- File Handling ---} > > {$define status(a) IOResult} > {$define open(a, b) assign(a,b)} > > {--- Read enumerated types / booleans from files ---} > > {$define readlnenum(a,b,c) readenum(a,b,c);readln(a)} > {$define readlnbool(a,b) readbool(a,b);readln(a)} > > Then create a UNIT for inclusion in the Pascal modules to do some other > bits: > > UNIT OS_linux; > > INTERFACE > > USES > const_type; > > TYPE > Tstring = String(2048); > Pstring = ^String; > > FUNCTION LoCaseStr(CONST s : string) : Tstring; asmname > '_p_locase_str'; > PROCEDURE LoCaseString(VAR s : string); asmname '_p_locase_string'; > PROCEDURE DEC_zero(VAR param; ch : char; size : longint ); asmname > 'memset'; > > FUNCTION pad(str : string; fill : char; size : integer) : linestring; > PROCEDURE linux_reset( VAR ip_file : TEXT); > > PROCEDURE ReadBool (VAR f : TEXT; VAR ans : BOOLEAN); > PROCEDURE ReadEnum (VAR f : TEXT; VAR ans; CONST IDs : ARRAY OF > PString); > PROCEDURE WriteEnum (VAR f : TEXT; VAR EnumVal; CONST IDs : ARRAY [m .. > n : Integer] OF PString); > > CONST {This is just an example} > ModeIDs : ARRAY [0..2] of PString = (@'interactive', > @'batch', > @'batch_with_display'); > > IMPLEMENTATION > {************************************************************************* > *******************************************} > FUNCTION pad(str : STRING; fill : CHAR; size : Integer) : linestring; > > VAR > returned_string : linestring; > i, len_str : INTEGER; > > BEGIN > returned_string := str; > > len_str := length(str); > IF len_str > 255 THEN > len_str := 255; > > FOR i := (len_str+1) TO size DO > returned_string := returned_string + fill; > > pad := returned_string; > END; > {************************************************************************* > *******************************************} > > {************************************************************************* > *******************************************} > PROCEDURE linux_reset( VAR ip_file : TEXT); > > BEGIN > {$I-} { Disable I/O error checking } > reset(ip_file); > {$I+} > END; > {************************************************************************* > *******************************************} > > {************************************************************************* > *******************************************} > {*** Enumerated types > ***} > {************************************************************************* > *******************************************} > PROCEDURE ReadWord (VAR f : TEXT; VAR s : String); > > CONST > SpaceCharacters = [' ',#9]; > WordChars = ['A'..'Z', 'a'..'z', '_', '0'..'9']; { > Allowed characters } > > BEGIN > s:= ''; > WHILE f^ IN SpaceCharacters DO { > Skip over whitespace and blank lines } > IF EOLN(f) > THEN READLN(f) > ELSE GET(f); > > WHILE NOT EOF (f) AND NOT EOLn (f) AND (f^ IN WordChars) DO { > Build string from WordChar characters } > BEGIN > s:= s + f^; > GET (f) > END > END; > {************************************************************************* > *******************************************} > > {************************************************************************* > *******************************************} > PROCEDURE ReadBool (VAR f : TEXT; VAR ans : BOOLEAN); > > VAR s : TString; > > BEGIN > ReadWord (f, s); > { Read word from text file } > LoCaseString (s); > { Change to lower case } > IF s = 'false' THEN > { Assign logical based on value } > ans := FALSE > ELSE IF s = 'true' THEN > ans := TRUE > ELSE > BEGIN > writeln('Error reading boolean from file.'); > halt > END > END; > {************************************************************************* > *******************************************} > > {************************************************************************* > *******************************************} > PROCEDURE ReadEnum (VAR f : TEXT; VAR ans; CONST IDs : ARRAY OF PString); > > TYPE > enum = (z_a, z_b, z_c, z_d, z_e, z_f, z_g, z_h, z_i, z_j, z_k, z_l, > z_m); { Dummy enumerated type } > > VAR > s : TString; > temp : enum; > > BEGIN > ReadWord (f, s); { Read > word from text file } > LoCaseString (s); { Change > to lower case } > temp:= Low(enum); { Select > first value } > WHILE (temp <= enum(High (IDs))) AND { While > value < max value AND} > (LoCaseStr (IDs [ord(temp)]^) <> s) DO Inc (temp); { > string not yet found, increase value} > > IF ord(temp) <= High (IDs) { If > string was found } > THEN > enum(ans) := temp { assign > value to variable } > ELSE > BEGIN > writeln('Error reading enumerated type from file.'); > halt > END > END; > {************************************************************************* > *******************************************} > > {************************************************************************* > *******************************************} > PROCEDURE WriteEnum (VAR f : TEXT; VAR EnumVal; CONST IDs : ARRAY [m .. n > : Integer] OF PString); > > TYPE > enum = (z_a, z_b, z_c, z_d, z_e, z_f, z_g, z_h, z_i, z_j, z_k, z_l, > z_m); { Dummy enumerated type } > > BEGIN > WRITE (f, IDs [ord(enum(EnumVal))]^) > END; > {************************************************************************* > *******************************************} > END. > > Using {*V*} for DEC syntax and {*L*} for gpc syntax, module headers look > like this: > > {*V*}[INHERIT('gen_lib.pen','globals.pen')]MODULE example_mod; > {*L*}{MODULE example_mod interface;} > {*L*}{ export example_mod =(task1);} > {*L*}{ PROCEDURE task1(request:integer);} > {*L*}{END.} > > {*L*}{MODULE example_mod implementation;} > {*L*}{#INCLUDE <os_linux.h>} > {*L*}{USES os_linux, gen_lib, globals;} > VAR > ... > [GLOBAL]PROCEDURE task1(request:integer); > > Unit headers look like this: > > {*V*}[ENVIRONMENT ('globals.pen')]MODULE globals_mod; > {*L*}{UNIT globals;} > {*L*}{#include <os_linux.h>} > {*L*}{INTERFACE} > > VAR > ... > > {*L*}{IMPLEMENTATION} > > END. > > And some other changes are: > > {*V*} a:= ZERO; > {*L*} zero(a); > {*V*} a : array [1..3] of double:= ZERO; > {*L*} a : array [1..3] of double:= (0,0,0); > {*V*} OPEN(myfile,"filename.dat",ERROR:=CONTINUE, HISTORY:= OLD); > {*L*} OPEN(myfile,"filename.dat"); linux_reset(myfile); > {*V*}READLN(myfile,Booleanvar); > {*L*}READLNBOOL(myfile, Booleanvar); > {*V*}READLN(myfile,Enumeratedvar); > {*L*}READLNENUM(myfile, Enumeratedvar, EnumstringIDs); > > Where ERROR:=CONTINUE is used with READLN, bracket the READLN with {I-} > and {I+}. These are compiler directives recognised by GNU Pascal (and > ignored by DEC Pascal) which disable I/O error checking. > > Replace SYS$OUTPUT with /dev/stdout. > Replace SYS$INPUT with /dev/stdin. > > 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.

1 0

Porting from DEC pascal to GPC
by Rob Koopman 06 Feb '03

06 Feb '03

Hello: We are investigating to port about 400.000 lines of DEC Vax Pascal (started as VMS application later ported to OSF1 UNIX). One of our concerns is the maturity of the GPC environment. During our initial tests we encountered some compiler problems (segfault, internal error). An obvious question is did someone else try this before. ( DEC Pascal has funny extentions) Regards, Rob Koopman

3 2

Re: Porting from DEC pascal to GPC
by Rob Koopman 06 Feb '03

06 Feb '03

Martin Liddle wrote: We ported an application with a similar number of lines to yours from Extended Pascal and it now runs very well. What operating system and hardware are you moving the application to? We port a library (as in University library) application to SUN Solaris for hardware like Sun V480. Regards Rob Koopman

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