Gpc June 1999

gpc@gnu.de

22 participants
50 discussions

Files
by berend＠beard.nest.nl 01 Feb '02

01 Feb '02

* Moved (from: gpc) by Berend de Boer using timEd 1.10.b3+. Peter Gerwinski wrote in a message to Berend de Boer: PG> I tried to use Extended Pascal "binding" to assign a file PG> variable to an external -- existing -- file. I just copied PG> the "Assign" pro- cedure by Berend as published in PG> borland2ep.doc. It does not always work: I often get a PG> runtime error saying that the file did not exist. If you can repeat it, compile with another Extended Pascal compiler, for example Prospero's one. If that fails too, there is really something wrong with the code. But I suspect gpc. You're using which OS? Groetjes, Berend (-: fido: 2:281/527.23 email: berend(a)beard.nest.nl

4 3

Re: Huffman compression comes to GPC!
by Frank Heckenbach 03 Aug '99

03 Aug '99

"Dr A A Olowofoyeku" wrote: > I have just completed work on an Huffman compression unit which now > supports GPC. The unit exports two main (alternative) compression > functions and two decompression functions. The routines are "dead easy" > to use, and the compression ratio compares well with ZIP's "deflate". > > I have tried to make the code portable, and I believe that I have > achieved this (it works fine with TP, BP, Delphi, FreePascal, and GPC). > AFAIK there are no "endian" issues, but I stand corrected. Unfortunately, there seem to be some. Files compressed on a little-endian machine don't uncompress on a big-endian one (or vice versa). Comparing the same file compressed on both kinds of machines shows differences in byte ordering. I don't have the time to study the code throughly enough to say exactly what the problem it, but at first sight, WDBuf might be the problem, since it contains 16-bit words which are written to a file. To solve the problem, of course, you first have to decide if you want the data files to be little or big endian. If they're following some standard, this will be given, otherwise, if you invented the format, it's up to you. Let's assume you want them to be little endian. Convert each element of the buffer to little endian using the ConvertToLittleEndian procedure, e.g.: ConvertToLittleEndian (WdBuf [i], SizeOf (WdBuf [i])) You can do this either immediately after writing the values into the buffer, or before the BlockWrite. You don't need any ifdef for this -- the routine will simply not change the values on a little endian system. Similarly, before reading values from the buffer (e.g. after the BlockRead statements), convert them back using ConvertFromLittleEndian. BTW, if you want to test the changes and don't have access to a big endian system, you might use big endian data files (perhaps only for testing, if you want little endian data files otherwise), i.e. use ConvertToBigEndian and ConvertFromBigEndian instead of ConvertToLittleEndian and ConvertFromLittleEndian, and verify that you can still compress and decompress files correctly. If you need to still compile the code with BP, you can use the following routines which are part of a GPC compatibility unit for BP which will be included in the next GPC release. (Just install the unit below where BP will find it, but GPC won't, then do a `uses GPC' in the code, so BP will use the unit below, and GPC will use its own GPC unit.) Frank -- Frank Heckenbach, frank(a)fjf.gnu.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html unit GPC; interface const Bits_Big_Endian = False; Bytes_Big_Endian = False; Words_Big_Endian = False; Need_Alignment = False; MaxVarSize = $fff0; type SizeType = Word; procedure ReverseBytes (var Buf; Count : SizeType); procedure ConvertFromLittleEndian (var Buf; Count : SizeType); procedure ConvertFromBigEndian (var Buf; Count : SizeType); procedure ConvertToLittleEndian (var Buf; Count : SizeType); procedure ConvertToBigEndian (var Buf; Count : SizeType); function BlockReadLittleEndian (var aFile : File; var Buf; Count : SizeType) : SizeType; function BlockReadBigEndian (var aFile : File; var Buf; Count : SizeType) : SizeType; function BlockWriteLittleEndian (var aFile : File; const Buf; Count : SizeType) : SizeType; function BlockWriteBigEndian (var aFile : File; const Buf; Count : SizeType) : SizeType; implementation procedure ReverseBytes (var Buf; Count : SizeType); var i : SizeType; b : Byte; ByteBuf : array [1 .. MaxVarSize] of Byte absolute Buf; begin for i := 1 to Count div 2 do begin b := ByteBuf [i]; ByteBuf [i] := ByteBuf [Count + 1 - i]; ByteBuf [Count + 1 - i] := b end end; procedure ConvertFromLittleEndian (var Buf; Count : SizeType); begin if Bytes_Big_Endian then ReverseBytes (Buf, Count) end; procedure ConvertFromBigEndian (var Buf; Count : SizeType); begin if not Bytes_Big_Endian then ReverseBytes (Buf, Count) end; procedure ConvertToLittleEndian (var Buf; Count : SizeType); begin if Bytes_Big_Endian then ReverseBytes (Buf, Count) end; procedure ConvertToBigEndian (var Buf; Count : SizeType); begin if not Bytes_Big_Endian then ReverseBytes (Buf, Count) end; function BlockReadLittleEndian (var aFile : File; var Buf; Count : SizeType) : SizeType; var Result : SizeType; begin BlockRead (aFile, Buf, Count, Result); if InOutRes = 0 then ConvertFromLittleEndian (Buf, Count); BlockReadLittleEndian := Result end; function BlockReadBigEndian (var aFile : File; var Buf; Count : SizeType) : SizeType; var Result : SizeType; begin BlockRead (aFile, Buf, Count, Result); if InOutRes = 0 then ConvertFromBigEndian (Buf, Count); BlockReadBigEndian := Result end; function BlockWriteLittleEndian (var aFile : File; const Buf; Count : SizeType) : SizeType; var Result : SizeType; p : Pointer; begin GetMem (p, Count); Move (Buf, p^, Count); ConvertToLittleEndian (p^, Count); BlockWrite (aFile, p^, Count, Result); FreeMem (p, Count); BlockWriteLittleEndian := Result end; function BlockWriteBigEndian (var aFile : File; const Buf; Count : SizeType) : SizeType; var Result : SizeType; p : Pointer; begin GetMem (p, Count); Move (Buf, p^, Count); ConvertToBigEndian (p^, Count); BlockWrite (aFile, p^, Count, Result); FreeMem (p, Count); BlockWriteBigEndian := Result end; end.

3 2

GNU Pascal.
by Alejandro Villarroel 30 Jun '99

30 Jun '99

Is my first time with this, so I'll apreciate any help. I want to install Pascal in PCs with DOS, I have all the files required, but which are the steps to follow in order to install GNU Pascal. If I want to install it on a Windows platform, what I have to do? and what other files I will need? Thanks in advance Alejandro Villarroel

2 1

Re: compiler problem
by Frank Heckenbach 30 Jun '99

30 Jun '99

Michael Hofmann wrote: > Hi, > > the following little program doesn't run under gpc version 2.0(2.7.2.1)! > > program lesen (infile,output); > > const > n = 100; > > type > text = File of char; > filearray = array[1..n] of real; > > var > i : integer; > infile : text; > filearray1 : filearray; > > begin > reset(infile); > for i:= 1 to n do > begin > read(infile,filearray1[i]); > write(filearray1[i]); > end; > > end. > > I get the compiler message:gpc: Internal compiler error: program gpc1 got > fatal signal 6 > I know that the program runs under a Sun-Compiler! > > when I substitute filearray = array[1..n] of real; by > filearray = array[1..n] of integer; , then compilation is successful. The problem is your declaration: > type > text = File of char; According to the Pascal standards, a `Text' file is similar to a `File of Char', but not the same. In particular, one can read numeric data from `Text' files, but not from `File of Char'. If the Sun compiler allows this, that's non-standard behaviour, which GPC currently does not support. However, if you just remove this declaration, it should work, since `Text' is a predefined type in Pascal. If you then still get problems with GPC, please upgrade to a recent alpha or beta version (already much more stable than 2.0), available from: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/ ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/ Frank -- Frank Heckenbach, frank(a)fjf.gnu.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

1 0

compiler problem
by Michael Hofmann 30 Jun '99

30 Jun '99

Hi, the following little program doesn't run under gpc version 2.0(2.7.2.1)! program lesen (infile,output); const n = 100; type text = File of char; filearray = array[1..n] of real; var i : integer; infile : text; filearray1 : filearray; begin reset(infile); for i:= 1 to n do begin read(infile,filearray1[i]); write(filearray1[i]); end; end. I get the compiler message:gpc: Internal compiler error: program gpc1 got fatal signal 6 I know that the program runs under a Sun-Compiler! when I substitute filearray = array[1..n] of real; by filearray = array[1..n] of integer; , then compilation is successful. Michael. mail:hofmann@ph2.uni-koeln.de

2 1

Installation Trouble (Windows 98)
by Brian M. Begg 28 Jun '99

28 Jun '99

June 26, 1999 Hello: I am having trouble installing all of the MINGW32 based tools that I downloaded as zip files. I am in Windows 98, and I have the WINZIP utility for unzipping. It works with just about all of these (downloaded) zipped based tools except: "gcc-2_8_1" and "gas-980119" An error message keeps coming (up when I unzip) that says: "Error: cannot create C:/MINGW32/bin/c++filt.exe. Please press F1 for help. " Also, for "mingw32-980105" an error msg: "cannot create C:/MINGW32/samples/dlltest/rcs/dll.c,v. Please press F1 for help." What should I do? Please help if u can. Best Regards, Brian Begg --------> brianb(a)ixpres.com p.s. e-mail anytime you like.

2 1

GPCC (BP compatibility compiler front end for GPC)
by Dr A A Olowofoyeku 25 Jun '99

25 Jun '99

Hi all I have just put a copy of the latest incarnation of GPCC (a Borland-Pascal compatibility compiler front end for GPC) on : http://freeweb.digiweb.com/computers/African_Chief/gpcc200.zip Please download for testing and please report all bugs, problems and suggestions to me. This is eventually going to be released as part of the main GPC distribution, so your input will be appreciated at this stage. The main goal of GPCC is to implement some of the main features of the Borland Pascal command line compilers (TPC and BPC), under GPC, by; [a] supporting some of the Borland compiler options and switches [b] reading options and switches from a configuration text file (named by default in the Borland style with a ".cfg" extension) [c] attempting to identify from a basic parsing of the first few lines of a source file whether the source file is a UNIT/MODULE or PROGRAM/UNIT, and supplying appropriate parameters to the linker [d] looking (if no extension is supplied for a filename) for the file, with the following extensions, and in the following order; [a] ".pas" [b] ".p" [c] ".pp" [d] ".dpr" This is really meant to assist those coming to GPC from a BP/TP or Delphi background. It is *not* designed to replace "make" or such tools which unix and linux gurus are accustomed to. The real object is to reduce the numerous GPC compiler switches into something accessible to BP/TP/Delphi people. Therefore it will never do anything really complicated or clever. Please bear these points in mind when making comments or suggestions. One of the main things I am looking to comments about on is whether I have correctly interpreted the BP parameters in converting them to GPC parameters. I do not have a definitive list (with full explanations/descriptions) of all the GPC compiler and linker parameters, so if there are gaps in my implementation, please supply the necessary information to do it correctly. Thanks! Best regards, The Chief -------- Dr. Abimbola A. Olowofoyeku (The African Chief) Email: laa12(a)keele.ac.uk Homepage: http://ourworld.compuserve.com/homepages/African_Chief/ Author of: Chief's Installer Pro v5.10 for Win32 ftp://ftp.demon.co.uk/pub/ibmpc/win95/apps/chief32/chief510.zip

1 0

Latest GPC + Solzris 7 + egcs/gcc
by Jovan Ilic 22 Jun '99

22 Jun '99

Did anybody compile gpc under Solaris 2.7 and egcs 1.1.1->gcc2.95 or gcc-2.8.1? I always get signal 6 when it starts compiling gpc files. Thanks, ilic(a)thetausa.com

2 3

re: snapshot
by Russ Whitaker 22 Jun '99

22 Jun '99

hi Frank As you know and I Just found out moving the tree from /usr/lib to /usr/local/lib doesn't work too well so I recompiled: make dist clean make clean (just in case ) ./configure --prefix=/usr/local then make LANGUAGES=pascal CFLAGS="-O2" until it crashed, then make LANGUAGES=pascal until it crashed, then created 2 directories and a soft link, ar->/usr/bin, then make LANGUAGES=pascal make pascal.install All this gave me a partially optimized gpc installed under /usr/local and working nicely thanks Russ

2 1

GPC BUG: Initializer for tagged variant records does not work
by pdietrich＠synstar.de 18 Jun '99

18 Jun '99

Hello, I found the following bug in the Beta version of GPC. Best regards, Peter Dietrich -------------------- GPC-Version (gpc -v): Reading specs from C:\usr\local\lib\gcc-lib\i386-mingw32\2.8.1\specs gpc version 19990118, based on gcc-2.8.1 System-Version: Windows NT 4.0 on i386 Problem description: Variant records with tag fields cannot be initialized. The following program is not accepted by the compiler: program test (output); type t = record f1 : integer; case tag : integer of 0: (i : integer); 1: (r : real); end; var r : t value (1, 1, 3.14); begin writeln (r.f1, r.tag, r.r); end. The error message is: test3.pas:10: incompatible types in initialization test3.pas:10: initial value is of wrong type If I omit the 3.14 compilation succeeds but only f1 and tag are initialized.

4 3

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 June 1999