July 2000 - Gpc

gpc on HP-UX
by S. Achterop IWI-120 3932 12 Jul '00

12 Jul '00

Hello, Regrettably the new gpc-20000705 still does not compile on HP-UX 10-20. The problem from the buglist still seems to exist. The make now ends with: make[2]: Entering directory `/rug104/home6/users/sietse-tijdelijk/gpc-build/gcc/p/rts' ../.././xgpc -B../.././ -c -I. -W -Wall - ........... /rug103/home3/users/sietse/tijdelijk/gcc-2.95.2/gcc/p/rts/error.pas gpc1: warning: -g is only supported when using GAS on this processor, gpc1: warning: -g option disabled. ... gcc-2.95.2/gcc/p/rts/error.pas: In function `Formatstr': ... gcc-2.95.2/gcc/p/rts/error.pas:538: internal error--unrecognizable insn: (insn 17 16 19 (set (zero_extract:SI (reg:SI 98) (const_int 32 [0x20]) (const_int 0 [0x0])) (reg:SI 99)) -1 (insn_list 14 (insn_list 16 (nil))) (expr_list:REG_DEAD (reg:SI 99) (nil))) make[2]: *** [error.o] Error 1 make[2]: Leaving directory `/rug104/home6/users/sietse-tijdelijk/gpc-build/gcc/p/rts' make[1]: *** [pascal.rts] Error 2 make[1]: Leaving directory `/rug104/home6/users/sietse-tijdelijk/gpc-build/gcc' make: *** [all-gcc] Error 2 Regards, Sietse

1 0

Re: nestbug: bugs in gpcc with the use of --nested-comments
by Frank Heckenbach 12 Jul '00

12 Jul '00

Tom Schneider wrote: > This code demonstrates a bug in gpc: > > GNU Pascal version 20000707, based on gcc-2.95.2 19991024 (release). > > which when called on this program as: > > gpc --standard-pascal --nested-comments --transparent-file-names $nestbug.p -o $nestbug > > will object as follows: > > nestbug.p:54: parse error before `Documentation' > > because, although the --nested-comments is on, it still can't handle > this unbalanced right curlie bracket: } What was called `--nested-comments' in previous GPC versions, is now called (more precisely, IMHO) `--no-mixed-comments'. The option `--nested-comments' now means really nested comments like `{ { } }'. BTW, this *is* described prominently in the NEWS file or the News chapter in the GPC manual. > 2. ADDITIONAL BUG: Note also that GPC capitalizes the word > "Documentation", which is confusing and it should not do. Someone doing a > case sensitive search would not find the problem! That's why a case-sensitive search through Pascal code is a bad idea, I guess... > This occurs in other > places in the code. GPC should NEVER change cases!!!! (Oh, I see. In > German one capitalizes nouns. Perhaps this is why you thought to do it. > The rest of the world does not and it will cause confusion and trouble. > How about creating a --German command line option? :-) It's not about German at all, as you should've noted from the following facts: - The original GPC was created in Finland. - GPC also capitalizes verbs, adverbs, perpositions, non-words, etc. Seriously, I think we've discussed this matter before, in connection with `--transparent-file-names'. It's about avoiding conflicts with (e.g.) libc identifiers. When GPC supports some other form of name mangling, we can get away with this capitalization. If you like to offer your help, be welcome, otherwise this will be done according to our time schedules... > { > I infer that when comments are parsed gpc does not remember the kind of > starting comment. It does with `--no-mixed-comments'. > 4. If the curlies around the above paragraph are deleted, the message is: > > nestbug.p:92: unterminated string or character constant > nestbug.p:83: possible real start of unterminated constant > > The program is sensitive to single quote marks! Of course. Since the comment was closed (though unintentionally, see above), GPC expects Pascal code, and a single quote in Pascal code is quite significant. > The whole comment skipping code needs a careful overhaul! Quite the opposite: It's just had a careful overhaul which implied a redefinition of one option. Please change your command-line accordingly. > The program does a successful goto to the end of the code from > the halt routine, so that bug is FIXED. :-) :-) Thank you! Fine. (But you are aware that a Halt routine which does exactly this is already built in?) Frank -- Frank Heckenbach, frank(a)g-n-u.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

nestbug: bugs in gpcc with the use of --nested-comments
by Tom Schneider 12 Jul '00

12 Jul '00

program nestbug(output); (* nestbug: bugs in gpcc with the use of --nested-comments 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 http://www.lecb.ncifcrf.gov/~toms/ *) label 1; (* end of program *) const (* begin module version *) version = 1.00; (* of nestbug.p 2000 July 11 1.00; 2000 July 11 origin *) updateversion = 1.00; (* defines lowest acceptable current parameter file *) (* end module version *) (* begin module describe.nestbug *) (* name nestbug: bugs in gpcc with the use of --nested-comments synopsis nestbug(output: out) files output: messages to the user description This code demonstrates a bug in gpc: GNU Pascal version 20000707, based on gcc-2.95.2 19991024 (release). which when called on this program as: gpc --standard-pascal --nested-comments --transparent-file-names $nestbug.p -o $nestbug will object as follows: nestbug.p:54: parse error before `Documentation' because, although the --nested-comments is on, it still can't handle this unbalanced right curlie bracket: } examples documentation see also {GPC will also object to the } shell.p {program at} http://www.lecb.ncifcrf.gov/~toms/delila/shell.html author Thomas Dana Schneider bugs 1. See above. 2. ADDITIONAL BUG: Note also that GPC capitalizes the word "Documentation", which is confusing and it should not do. Someone doing a case sensitive search would not find the problem! This occurs in other places in the code. GPC should NEVER change cases!!!! (Oh, I see. In German one capitalizes nouns. Perhaps this is why you thought to do it. The rest of the world does not and it will cause confusion and trouble. How about creating a --German command line option? :-) 3. The use of the unbalanced bracket was legitimate in the shell program as part of a quoted string inside the documentation comments. { I infer that when comments are parsed gpc does not remember the kind of starting comment. It should recall that the comment of this documentation began with a left-parenthesis-astrisk, and so should ignore everything until it encounters an astrisk-right parenthesis. Apparently it doesn't and is sensitive to the curlie brackets. (The reverse should hold inside a curlie bracket comment of course.) } 4. If the curlies around the above paragraph are deleted, the message is: nestbug.p:92: unterminated string or character constant nestbug.p:83: possible real start of unterminated constant The program is sensitive to single quote marks! I had the word "doesn't" in the bugs section, and it blocked the case mentioned above! The curlie brackets above protect the single quote! The whole comment skipping code needs a careful overhaul! It should not be looking at quotes at all during comment skipping! technical notes The program does a successful goto to the end of the code from the halt routine, so that bug is FIXED. :-) :-) Thank you! *) (* end module describe.nestbug *) (* begin module halt *) procedure halt; (* stop the program. the procedure performs a goto to the end of the program. you must have a label: label 1; declared, and also the end of the program must have this label: 1: end. examples are in the module libraries. this is the only goto in the delila system. *) begin writeln(output,' program halt.'); goto 1 end; (* end module halt version = 'delmod 6.16 84 mar 12 tds/gds'; *) (* begin module nestbug.themain *) procedure themain; (* the main procedure of the program *) var parameterversion: real; (* parameter version number *) begin writeln(output,'nestbug ',version:4:2); halt; end; (* end module nestbug.themain *) begin themain; 1: end.

1 0

error in util.c 2nd
by David Kredba 10 Jul '00

10 Jul '00

I found, that the file gcc-2.95.2.diff and gcc-2.95.1.diff has zero byte size. After patching (patch is automatically made by ./configure) to the file stor-layout.c there in the stor-layout.c is not declared "size_volatile". While linking gpc1.exe ld returns error. I copy gcc-2.95.diff to gcc-2.95.2.diff and run ./configure again, after removing all new files. ./Configure preciously find gcc-2.95.2 and apply patch. In stor-layout.c is now present missing declaration. The file util.c is after patching OK. Gpc1.exe, xgpc.exe and gpc-cpp.exe are succesfuly created. But after, while make building libgcc2.a I obtain this error message : In file included from ./libgcc2.c:48: include/sttdef.h:255: conflicting types for ' wchar_t' d:/dj/include/stdlib.h:39: previous declaration of ' wchar_t' Program cc1 got fatal signal 33. I have djdev203 header files. David Kredba

1 0

Re: test results
by Frank Heckenbach 10 Jul '00

10 Jul '00

Prof Abimbola A Olowofoyeku wrote: > I can't run the test suite as presented (under Mingw and Cygwin), > because I keep getting an error "*.pas: no such file" or something > like that. Of course I can compile the source files singly or run a "for" > loop at the command line - but presumably, you want the test suite > to run on all platforms ... I'm making use of filename quoting and expansion in a non-trivial way in the tests script, and that's probably the reason for the failure because Dos shells have some problems with (read: no support for ;-) filename expansion... Interestingly enough, it works well under DJGPP... but only if I set SHELL to the path of bash (which I do by default). So, does it work if you set SHELL (I assume you have bash and GNU make installed), or add the line SHELL = /bin/sh to p/test/Makefile (or maybe `SHELL = <full_path_to>sh.exe' -- but at least under DJGPP that's not necessary because make does this automagically)? Frank -- Frank Heckenbach, frank(a)g-n-u.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

Re: 'include' and 'lib' files
by Nick Burrett 10 Jul '00

10 Jul '00

Anuradha <Anuradha(a)adcc.alcatel.be> writes: > When i try to build a cross-compiler for > target i386-solaris machine with host :sparc-solaris, > > it asks me for the lib and the include files of i386-solaris . > > I don't have an i386-solaris machine here.Can you tell me where i can > find these 'lib' and 'include' files? You can only get these from a i386-solaris installation. If you don't have such an installation, then you can't get them. Regards, Nick.

1 0

GPC alpha release and GPC CVS server
by Peter Gerwinski 10 Jul '00

10 Jul '00

Hello, folks! This is the announcement of a new alpha version of GPC: gpc-20000705 We also have set up a CVS server where you can always check out the current development snapshot. Alpha snapshots are now going to be released much more frequently. At the same time we have updated the GPC WWW pages. They now contain the GPC documentation in HTML, DVI and PS format which are updated automatically with the GPC source. The instructions below are an extract from the new `INSTALL' file. For a list of new features in this release, see the section `news' on the GPC WWW pages and/or in the GPC documentation. For fixed bugs, see the GPC TODO list at the same places. Have fun, the GNU Pascal development team Where and what to download ========================== The master server for GNU Pascal is `agnes.dida.physik.uni-essen.de'. Official and beta releases of the compiler with sources and binaries for many platforms as well as other GNU Pascal related files can be found in `ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/' You can find binary distributions for many platforms in the subdirectory `binary'. The archive files are named `gpc-VERSION.PLATFORM.EXTENSION' - for example `gpc-2.1.alpha-unknown-linux-gnu.tar.gz' for GPC version 2.1 on an Alpha workstation running the Linux kernel with GNU C Library, or `gpc-20000616.i586-pc-djgppv201.zip' for GPC version 20000616 on an i586 PC running DOS with DJGPP version 2.01. After you have downloaded the correct archive file for your platform, please read the installation notes on how to install such a binary distribution. If you are running Dos or MS Windows, you will need additional tools - see "What else to download and where" below. Current snapshots ----------------- GNU Pascal is subject to steady development. You can download the current snapshot (source only, use at your own risk) via anonymous FTP from: `ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/' or via anonymous CVS from: CVS root: :pserver:anonymous@agnes.dida.physik.uni-essen.de:/usr/local/cvsroot Password: anonymous Command: checkout gpc Please read the installation notes on how to compile the source from a distribution or a CVS checkout. Compiling GPC ============= The preferred way to distribute GNU software is distribution of the source code. However, it can be a non-trivial exercise to build GNU Pascal on some non-Unix systems, so we also provide ready-to-run binaries for a number of platforms. (See above for how to install a binary distribution.) GPC is based on the GNU Compiler Collection, GNU CC or GCC. You will need the GCC sources to build it. It must be the same version as the one GPC is implemented with - `version 2.95.x' as of this writing. Although you need GCC to build the GNU Pascal compiler, you don't need GCC to compile Pascal programs once GNU Pascal is installed. (However, using certain libraries will require compiling C wrappers, so it is a good idea to install the C compiler as well.) Because GNU Pascal shares its back-end with GCC, it should run on any system supported by GCC. A full list of platforms supported by GCC can be found in the GCC installation instructions. The GCC source can be obtained from any mirror of the GNU FTP site, `ftp://ftp.gnu.org/gnu/gcc/'. The "core" distribution is sufficient for GPC. Here is the generic procedure for installing GNU Pascal on a Unix system. See below for extra information needed to install GPC on DOS-like platforms. 1. Checking the prerequisites Make sure that GNU make is installed. (In the following, we will simply speak of `make' when invoking GNU make; you might need to call `gmake' instead.) For extracting the example programs from the documentation to the `doc/docdemos' directory a non-crippled `sed' is needed. GNU sed is known to work. If you have checked out the GPC source from CVS, you will have to rebuild most derived files, so you will need additional tools: `bison', `flex', `makeinfo', `gperf', and `autoconf'. Make sure that these are installed. If you want to build the GPC WWW pages you will also need: `texi2html' version 1.61 (older versions are missing some needed features; newer versions suffer from a bug), `texi2dvi', TeX, `gzip', `dvips', `dviselect', and `dviconcat'. If you run into trouble during the installation process, please check whether you are using outdated versions of the required utilities and upgrade if necessary. The GNU versions of the packages above are available from the GNU FTP server (ftp://ftp.gnu.org) or any of its mirrors. Package PACKAGE is usually located in the directory `gnu/PACKAGE'. 2. Unpacking the source From a directory of your choice (e.g. `/home/fred'), unpack the GCC and GNU Pascal source distributions. This will create separate subdirectories for GCC and GPC. Let us assume `gcc-2.95.1' and `gpc-20000535' in this example. % cd /home/fred % gzip -c -d gcc-core-2.95.1.tar.gz | tar xf - % gzip -c -d gpc-20000535.tar.gz | tar xf - `cd' to the GPC directory and move the contents (a subdirectory `p') to the subdirectory `gcc' of the GCC directory: % cd /home/fred/gpc-20000535 % mv p /home/fred/gcc-2.95.1/gcc/ It is recommended, though not required, to use a separate directory for building the compiler, rather than compiling in the source directory. In this example, let us create `/home/fred/gpc-build' for this purpose: % mkdir /home/fred/gpc-build If you use a separate directory, you do not need to write into the GCC source directory once you have patched the GCC source (see below), and can build GPC for more than one platform from the same source tree. In case you are re-using a directory where you have already built GCC and/or GPC for a different target machine, do `make distclean' to delete all files that might be invalid. One of the files this deletes is `Makefile'; if `make distclean' complains that `Makefile' does not exist, it probably means that the directory is already suitably clean. 3. Configuring and building GCC GNU Pascal is automatically configured with GCC. Configuration of GCC is treated in depth in the GCC installation instructions. The normal procedure is as follows: `cd' to the GPC build directory. From there, run the `configure' script in the GCC source directory: % cd /home/fred/gpc-build % /home/fred/gcc-2.95.1/configure --enable-languages=pascal This creates all the necessary config files, links and Makefile in the GCC object directory. Note 1: The configuration will prompt you for patching the GCC source for GPC support, so you need write access to that directory. All changes to GCC are surrounded by `#ifdef GPC ... #endif', so they should not interfere when you build a C compiler from this source tree. Note 2: The `--enable-languages=pascal' option means that we only want to build the Pascal compiler and not, for instance, the C++ compiler. Note 3: The standard directory for installing GCC and GPC is `/usr/local/lib'. If you want to install files to an alternate directory DIR, specify `--prefix=DIR' when you run `configure'. 4. Putting other GNU tools in place Some environments require other GNU tools (such as the GNU assembler or linker) instead of the standard system tools for GCC to work. (See the GCC installation instructions for details.) If this is the case for your system, install the required tools in the GPC build directory under the names `as', `ld', or whatever is appropriate. This will enable the compiler to find the proper tools for compilation of the program `enquire' (a part of GCC) and to install the GNU tools to a place where they are found by GCC but do not interfere with the standard system tools. Alternatively, you can do subsequent compilation using a value of the `PATH' environment variable such that the necessary GNU tools come before the standard system tools. 5. Compiling GPC Once you are satisfied with the configuration as determined by `configure', you can build the compiler: % make Notice that this procedure will build the C compiler (and maybe some other compilers) too, because that is used to compile the GPC runtime library. Optionally, you may supply CFLAGS, LDFLAGS or RTSFLAGS. CFLAGS is used for compiler and RTS, RTSFLAGS are for RTS only, i.e.: `make CFLAGS="-O2" RTSFLAGS=-Wall' 6. Completing the installation When everything has been compiled, you can check the installation process with: % make -n install To complete the installation, run the command `make install'. You need write access to the target directories (`/usr/local/bin', `/usr/local/lib', `/usr/local/info', `/usr/local/doc', and `/usr/local/man' in this example), so this is usually done as `root': % su -c "make install" If you want to install *only* the Pascal compiler (for example if you already have the correct version of GCC installed), `cd' to the `gcc' subdirectory of the build directory (e.g. `/home/fred/gpc-build/gcc') and run `make pascal.install'. This installation process does *not* overwrite existing copies of `libgcc.a' or `specs', should they exist. Also from the `gcc' subdirectory you can do some more "exotic" builds. For instance, you can build the GPC WWW pages by typing `make pascal.html' or a binary distribution by typing `make pascal.bindist'. See the `Makefile' in that directory for more examples. Have fun with GPC!

3 4

Re: test results
by Frank Heckenbach 10 Jul '00

10 Jul '00

Russ Whitaker wrote: > Hi > > Installed the newest release today. > Ran test suite. Results: > > total 1271 > pass 192 > skip 2 > fail 1077 > > But that's somewhat misleading. almost all the error msgs were > " ... is dangerous. Use lseek64 instead". > > Is there a simple fix? Which OS and libc version? Could you please post the complete error message (only one if they're all the same)? Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

2 1

GPC 20000705 (Win32 binaries released)
by Prof Abimbola A Olowofoyeku 10 Jul '00

10 Jul '00

Hi all I have uploaded Win32 binaries for the latest GPC beta (20000705) to agnes. There are two packages - one for Mingw (msvcrt version) and one for Cygwin (v1.x). Take your pick, but I recommend the Mingw release. You can get a copy from here: ftp://agnes.dida.physik.uni-essen.de/home/chief/ Enjoy! Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) Author of: Chief's Installer Pro v5.22.1 for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm Email: African_Chief(a)bigfoot.com

1 0

test results
by Russ Whitaker 09 Jul '00

09 Jul '00

Hi Installed the newest release today. Ran test suite. Results: total 1271 pass 192 skip 2 fail 1077 But that's somewhat misleading. almost all the error msgs were " ... is dangerous. Use lseek64 instead". Is there a simple fix? Thanks, Russ

1 0