Gpc January 1997

gpc@gnu.de

11 participants
26 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

gpc linking problem
by Krzysztof Kwapien 17 Feb '97

17 Feb '97

I wrote the hello world program. begin writeln('Hello World'); end. I compiled it with gpc -o hello hello.pas and it Worked!! But when i tried to compile it with gpc -c hello.pas <- this worked gpc -o hello hello.o <- this crashed with a SIGSEGV ..... it crashed when linking. What's the problem? ( I tried the -v option, and it seems as if some of the temporary files, where not linked in ) Because RHIDE also does it in the same manner it crashes too Help: kkwapien(a)mimuw.edu.pl

2 2

Re: need GPC Developers?
by Peter Gerwinski 31 Jan '97

31 Jan '97

According to Ronald Perrella: > I'd like to see if there is anything I can do to help > with GNU Pascal development. Is there a wish-list of > things people want? > You may want to put such a list on the Web Home page. > (if it was there, I could not find it...) There is such a wish-list in the documentation, section "How you can contribute to GNU Pascal". But you are right that it should get a more prominent place on the WWW site. Just to mention a few current problems: * Improve the documentation. I am, for example, not too content with the current order of things. It should start with something like "Introduction to GNU Pascal", then "How to compile a program", etc. * Write more example programs. * Make the "Borland compatibility package" portable. I implemented it for DJGPP, but it would be nice to have it at least for Linux, too. Also, the DOS Unit is still missing ... * Fix the bugs. (Section "Known bugs and inconveniences ..." of the documentation lists most of the bugs.) * Implement the missing parts of ISO Standard Pascal, Level 1, and of ISO Extended Pascal - or at least point out what is missing because I actually do not know and I do not find it really instructive to read the Standard Specifications. * Implement the missing parts of Borland Pascal. Implement Delphi and Pascal-SC. You see that we are in the lucky position that there are enough of open problems that you can choose that one you like best to see been solved. ;-) I suggest just to try to write some useful programs with GNU Pascal (some of which we can publish as example programs), then you will run into some bugs and inconvenicences in the compiler and/or documentation. Once you know what you think to be the most annoying problem, try to fix it - and do not forget to contact us in case you succeed or have any questions. Thanks a lot for your offer! Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

Re: gpc linking problem
by Peter Gerwinski 31 Jan '97

31 Jan '97

According to Nils Bokermann: > According to Krzysztof Kwapien: > > But when i tried to compile it with > > gpc -c hello.pas <- this worked > > gpc -o hello hello.o <- this crashed with a SIGSEGV ..... > > it crashed when linking. > > Is it a ld-Problem? I've just tried it, but it works very well. I also suspect a ld-related problem here. Try to upgrade your "binutils". Ld version 2.7 is known to work with gpc 2.0. In case this does not solve the problem, please post some information about your system here, like Nils did: > Here is my system-info: > reality:~/pascal$ gpc -v > Reading specs from /usr/lib/gcc-lib/i486-unknown-linux/2.7.2.1.f.1/specs > gpc version 2.0(2.7.2.1.f.1) > reality:~/pascal$ ld -v > ld version 2.7 (with BFD 2.7.0.3) Good luck, Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

need GPC Developers?
by Ronald Perrella 30 Jan '97

30 Jan '97

Hi, I'd like to see if there is anything I can do to help with GNU Pascal development. Is there a wish-list of things people want? You may want to put such a list on the Web Home page. (if it was there, I could not find it...) -- Ronald Perrella perrella(a)mindspring.com Roswell, Georgia, USA.

1 0

Re: Again: g77 and gpc ...
by Peter Gerwinski 28 Jan '97

28 Jan '97

> [...] I just want to install ready-to-go gpc over my > gcc/g77 setup under emx09c. I noticed that that would replace gcc.a > from the original emx09c/gcc distribution. > Are there any negative experiences with that, or is it safe to do so? It should be save because gcc.a in the gpc distribution is (or: should be) the same as gcc.a in the gcc-2.7.2.1 distribution. I recommend you to try to run gpc with gcc.a from your gcc/g77 setup first. (I do not need to mention that you should backup your gcc.a first before replacing it with gpc's one, do I? ;-) Good luck, and let us know about your experience! Yours, Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

Again: g77 and gpc ...
by Stefan A. Deutscher 26 Jan '97

26 Jan '97

Hi, I noticed that there were some problems reported building gpc on a system that had the g77 patched gcc already. I just want to install ready-to-go gpc over my gcc/g77 setup under emx09c. I noticed that that would replace gcc.a from the original emx09c/gcc distribution. Are there any negative experiences with that, or is it safe to do so? Cheers. Stefan ============================================================================ Stefan A. Deutscher | (+1-423-) voice fax The University of Tennessee, Knoxville | UTK : 974-7838 974-7843 Department of Physics and Astronomy | ORNL : 574-5897 574-1118 401, A. H. Nielsen Building | home : 522-7845 522-7845 Knoxville, T.N. 37996-1200, USA | email: sad(a)utk.edu ============================================================================ Dictated with OS/2 Warp 4 VoiceType dictation.

1 0

Building GNU Pascal together with GNU Fortran.
by Niels Kristian Bech Jensen 26 Jan '97

26 Jan '97

Hi, Here is a small patch, which makes it possible to build GPC 2.0 using a GCC 2.7.2.1, that has been build with Fortran support (tested with G77 0.5.19). This could be useful for people, who (like me) needs to have both languages at hand. It changes the GCC version to 2.7.2.1.f.1 and adds the changes made for G77 to toplev.c: diff -rcp2N gpc-2.0/Makefile.in gpc-2.0.f.1/Makefile.in *** gpc-2.0/Makefile.in Mon Nov 18 03:31:33 1996 --- gpc-2.0.f.1/Makefile.in Sun Jan 26 17:32:05 1997 *************** *** 40,44 **** # GPCVERSION = `date +%y%m%d` GPCVERSION = 2.0 ! GCCVERSION = 2.7.2.1 CROSS = @cross@ --- 40,44 ---- # GPCVERSION = `date +%y%m%d` GPCVERSION = 2.0 ! GCCVERSION = 2.7.2.1.f.1 CROSS = @cross@ diff -rcp2N gpc-2.0/toplev.c gpc-2.0.f.1/toplev.c *** gpc-2.0/toplev.c Sat Sep 21 17:50:52 1996 --- gpc-2.0.f.1/toplev.c Sun Jan 26 17:30:28 1997 *************** int flag_unroll_loops; *** 392,395 **** --- 392,409 ---- int flag_unroll_all_loops; + /* Nonzero forces all invariant computations in loops to be moved + outside the loop. */ + + int flag_move_all_movables = 0; + + /* Nonzero forces all general induction variables in loops to be + strength reduced. */ + + int flag_reduce_all_givs = 0; + + /* Nonzero gets another run of loop_optimize performed. */ + + int flag_rerun_loop_opt = 0; + /* Nonzero for -fwritable-strings: store string constants in data segment and don't uniquize them. */ *************** struct { char *string; int *variable; in *** 553,556 **** --- 567,573 ---- {"unroll-loops", &flag_unroll_loops, 1}, {"unroll-all-loops", &flag_unroll_all_loops, 1}, + {"move-all-movables", &flag_move_all_movables, 1}, + {"reduce-all-givs", &flag_reduce_all_givs, 1}, + {"rerun-loop-opt", &flag_rerun_loop_opt, 1}, {"writable-strings", &flag_writable_strings, 1}, {"peephole", &flag_no_peephole, 0}, *************** rest_of_compilation (decl) *** 2965,2968 **** --- 2982,2987 ---- { loop_optimize (insns, loop_dump_file); + if (flag_rerun_loop_opt) + loop_optimize (insns, loop_dump_file); }); } -------------------------------------------------------- Niels Kristian Bech Jensen nkbj(a)image.dk "Chemists never die --- they just run out of reactants!"

1 0

Re: Apparent bug --> fixed.
by Peter Gerwinski 25 Jan '97

25 Jan '97

According to Stephen Lindholm: > I believe that this should not compile with a warning. > [...] I fixed the bug. Below is the diff for gpc-parse.y. You need Bison to produce gpc-parse.c out of it and to compile GPC, but you can also ignore the warning or surround the passage it with (*$W-*) ... (*$W+*) to suppress the warning. The bug is not serious enough that we release new binaries, but it will be fixed in the next release, of course. Thanks again for the report, Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/ 8< --------------------------------------------------------------------- --- gpc-parse.y.old Sat Jan 25 23:18:31 1997 +++ gpc-parse.y Sat Jan 25 23:18:35 1997 @@ -3847,7 +3847,7 @@ warning ("Extended Pascal does not allow parameters to HALT"); build_rts_call (p_HALT, $2); } | rts_file_open '(' actual_parameter optional_filename r_paren_or_error - { if (pedantic && $4 != NULL_TREE) + { if (pedantic && $4 != null_pointer_node) warning ("ISO Pascal does not allow file name parameter to reset/rewrite"); build_rts_call ($1, tree_cons (NULL_TREE, $3,

1 0

GNU Bulletin notes
by Peter Gerwinski 25 Jan '97

25 Jan '97

Hello! Some weeks ago, we were asked to write some notes about GNU Pascal for the GNU Bulletin. I do not know whether it is too late now, but here is a draft we could submit. Please post your comments/suggestions here as soon as possible, so we might get this into the January volume of the Bulletin. Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/ 8< ----------------------------------------------------------------- Forthcoming GNUs * Pascal GNU Pascal is a free 32-bit Pascal compiler. It is implemented as a Pascal front-end for GCC, the GNU compiler, thus it runs on all platforms supported by GCC and produces the same highly-optimized code. The current version 2.0 has passed all ISO 7185 level 0 conformance tests (but some problems on specific platforms where we suspect some general GCC problems), thus we consider it to be a valid level 0 Standard Pascal compiler. ISO 7185 level 1 is implemented, but not yet stable. Most of ISO 10206 Extended Pascal and Borland Pascal 7.0--including objects--is implemented plus some extensions from Pascal-SC (user-defineable operators) and native GNU extensions (e.g. min, max), but there is still a lot of work to do to fix all bugs, implement the missing features and improve the documentation. Any help is most welcome! The home ftp site of GNU Pascal is `kampi.hut.fi', directory `jtv/gnu-pascal/'. For more information, look into the inofficial `FAQ' in the `contrib' subdirectory. We also have a WWW home page `http://home.pages.de/~GNU-Pascal/' and a mailing list `gpc(a)hut.fi'. To get into the list, write an e-mail to `gpc-request(a)hut.fi'.

1 0

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 January 1997