Gpc January 1997

gpc@gnu.de

11 participants
26 discussions

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

25 Jan '97

According to Stephen Lindholm: > I believe this is a bug. I believe that this should not compile with a > warning. The warning is a bug in "-pedantic". Nothing serious. > gpc -Wall -ansi -pedantic --standard-pascal -o testfile testfile.p > If there are any typos, it is because I rekeyed the program. They would not > actually exist in the program. The compiler tells me that ISO Pascal does not > allow a file name parameter to reset/rewrite. I do not believe I am passing > one to rewrite. I believe the warning refers to the barbarous practice of > some compilers of requiring: > > rewrite (testfile, 'Test'); It's UCSD standard, and I find it much more useful than Extended Pascal's "bind" mechanism or Standard Pascal's method to mention "Test" in the program's parameter list (which your program doesn't, by the way) - where you have to type in the file name while the program runs. What do you think to be barbarous about that? > My mistake. Those testfiles in the program proper should be test. The program > name is testfile. Yes. Next time, please correct it in the e-mail *before* you post it. The time I needed to correct your program would have been better spent on correcting the bug you are pointing me to. However, thanks for the bug report. It will be corrected in the next release. 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

Borland compatibility package
by Peter Gerwinski 25 Jan '97

25 Jan '97

Hello, everybody! I have written a small Borland comptatibility package for GNU Pascal on the DJGPP platform. It contains my "BPcompat" Unit, renamed to "System", a (new) "CRT" Unit, and Sven's "BGI2GRX" Unit, renamed to "Graph". There is no "Printer" Unit yet because it caused unexpected problems to write one, but the patched "libgpc.a" allows you to print by assigning a file to "prn", rewriting it, etc. The package is not portable but a DOS(DJGPP)-only solution, so I do not really recommend to use it for your new projects. However it might be useful for porting existing applications. It is available in the contrib subdirectory of the GPC distribution, i.e. ftp://kampi.hut.fi/jtv/gnu-pascal/contrib/bpcompat.zip and ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/bpcompat.zip. I am setting up a link from the GNU Pascal home page to it, too. Have fun, 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

Apparent bug.
by Stephen Lindholm 24 Jan '97

24 Jan '97

I believe this is a bug. I believe that this should not compile with a warning. program testfile (input, output); var test: file of integer; i: integer; begin rewrite (testfile); for i := 1 to 10 do write (testfile, i); close (testfile); end. Compiled with: gpc -Wall -ansi -pedantic --standard-pascal -o testfile testfile.p If there are any typos, it is because I rekeyed the program. They would not actually exist in the program. The compiler tells me that ISO Pascal does not allow a file name parameter to reset/rewrite. I do not believe I am passing one to rewrite. I believe the warning refers to the barbarous practice of some compilers of requiring: rewrite (testfile, 'Test'); My mistake. Those testfiles in the program proper should be test. The program name is testfile. Please let me know if I am in error or when the bug will be fixed. (I'm not yet on the mailing list, so please forward a message directly to me.) Thank you.

1 0

GPC mailing list archives
by Peter Gerwinski 24 Jan '97

24 Jan '97

Hello, folks! I have the GPC mailing list archives to kampi and to agnes and set up a link to them in the GPC home page. Peter

1 0

Re: GNU Pascal and gcc/f77
by Peter Gerwinski 21 Jan '97

21 Jan '97

According to R. P. C. Rodgers, M.D.: > [...] I have just briefly tried to build your latest gpc with > gcc 2.7.2 with the GNU f77 patches applied. This results in an altered > version for gcc of "2.7.2.f.1" which the gpc configuration file rejects > as an inappropriate version. Do you have any plans to accommodate the > simultaneous installation of f77 and Pascal? We are working on merging Pascal into the GCC main distribution line. Once this is complete, you can install GNU Pascal together with GCC typing a command like `make LANGUAGES="C Pascal"'. Then all GNU Pascal patches will already be in the GCC source; additional GNU f77 patches should not spoil them, so it will probably work. And in case the f77 team and others are working on similar projects, it can become `make LANGUAGES="C C++ Objective-C Pascal Fortran Ada Basic Foo Bar"', one day ... (-: > Any suggested work-arounds > for my situation? Recently, Nils Bokermann sent a diff to this list which contains the necessary changes to `toplev.c'. We will include it into the GPC supplementary distribution (i.e. FAQ, WWW home page etc.), soon. Hope this helps, 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< ----------------------------------------------------------------------- From: Nils Bokermann <nilsb(a)reality.owl.de> Subject: GPC and G77 To: gpc(a)hut.fi Date: Mon, 13 Jan 1997 17:16:22 +0100 (MET) Hello! If trying to build the gpc-2.0 with the gcc-2.7.2.1 with the GNU Fortran enabled, will not run. There are some problems with the file toplev.c. Here is a simple diff, which worked at mine. --------cut-------------- diff -rcp2N gcc-2.7.2.1/toplev.c gcc-2.7.2.1.f.1/toplev.c *** gpc-2.0/toplev.c Fri Oct 20 17:56:35 1995 --- gpc-2.0.f.1/toplev.c Mon Nov 11 15:02:33 1996 *************** int flag_unroll_loops; *** 388,391 **** --- 388,405 ---- 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 *** 542,545 **** --- 556,562 ---- {"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) *** 2894,2897 **** --- 2911,2916 ---- { loop_optimize (insns, loop_dump_file); + if (flag_rerun_loop_opt) + loop_optimize (insns, loop_dump_file); }); } --------------cut------------- It's from the patch which came with GNU Fortran. Bye, Nils -- Nils Bokermann Johanneswerkstr. 90 Phone: +49 521 891279 33613 Bielefeld FAX: +49 521 550116 Germany "Wir wollen die Natur nicht erhalten -- Wir wollen nur ihre Dynamik nicht st"oren." _______________________________________________________________________________

1 0

GPC mailing list archive
by Peter Gerwinski 21 Jan '97

21 Jan '97

Hello, everybody! I am thinking about setting up an archive with all postings to the mailing list in the last two years (i.e. during the time I am on the list). The archive could consist of some gzipped mail folders to be downloaded from the GPC WWW home page. Okay? 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 mailing list archive
by Stefan A. Deutscher 21 Jan '97

21 Jan '97

On Tue, 21 Jan 1997 14:08:21 +0100 (MET), Peter Gerwinski wrote: >Hello, everybody! > >I am thinking about setting up an archive with all postings to the >mailing list in the last two years (i.e. during the time I am on >the list). The archive could consist of some gzipped mail folders >to be downloaded from the GPC WWW home page. > >Okay? Sure! Good idea. Thanks, mate! 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

GNU Pascal and gcc/f77
by rodgers＠nlm.nih.gov 21 Jan '97

21 Jan '97

Dear Gnu Pascal Team, First, congratulations on your great efforts in bringing Pascal into the GNU compiler family. I have just briefly tried to build your latest gpc with gcc 2.7.2 with the GNU f77 patches applied. This results in an altered version for gcc of "2.7.2.f.1" which the gpc configuration file rejects as an inappropriate version. Do you have any plans to accommodate the simultaneous installation of f77 and Pascal? Any suggested work-arounds for my situation? Thanks and Best Regards, Rick Rodgers

1 0

Graphics in Pascal
by Peter Gerwinski 20 Jan '97

20 Jan '97

Brin wrote: > I wrote the following small program to try out some graphics > routines [...] There is already BGI2GRX, a "Graph" compatible Unit, based on GRX20 and BCC2GRX, written by Sven Hilscher. > [...] Here is the program, any idea to > what I am doing wrong! The problem is that you are confusing some sizes of data types: > {****************************************************************} > Program Mode13h; > type > {Define some 'terms'} > byte = __byte__ integer; {8 bit unsigned integer} signed > word = __unsigned__ integer; {16 bit unsigned integer} 32 > Long = __longlong__ integer; {64 bit signed integer} correct, but used in wrong context (see below) If you correct them, your program runs fine. Below are the correct sizes for Intel X86 platforms. (I am thinking about implementing the identifiers below into GPC's standard vocabulary.) Type ByteInt = __byte__ Integer; (* 8 bit signed Integer *) Byte = __unsigned__ ByteInt; (* 8 bit unsigned Integer *) ShortInt = __short__ Integer; (* 16 bit signed Integer *) ShortWord = __unsigned__ ShortInt; (* 16 bit unsigned Integer *) (* Integer = __long__ Integer *) (* 32 bit signed Integer *) Word = __unsigned Integer; (* 32 bit unsigned Integer *) LongInt = __longlong__ Integer; (* 64 bit signed Integer *) LongWord = __unsigned__ LongInt; In addition, "unsigned long" in C has 32 bits, not 64: > {routines taken from include/sys/farptr.h} > {Puts a byte} > procedure _farnspokeb(offset: Long ; value: byte);External;C; > {Gets a byte} > function _farnspeekb(offset: Long ; value: byte):byte;External;C; (* Here's ^^^^^^^^^^^ another error ;*) Procedure FarNoSelectorPokeByte ( Offset: Word; value: Byte ); AsmName '_farnspokeb'; (* ;-) *) Function FarNoSelectorPeekByte ( Offset: Word ): Byte; AsmName '_farnspeekb'; (* (-; *) Hope this helps, 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: GNU Pascal, go32.h
by Peter Gerwinski 20 Jan '97

20 Jan '97

According to Brin: > I am trying to use the farptr.h library and the go32.h libaray. [...] > To use them I need _dos_ds, which is defined in the C library go32.h > but is not a function or a procedure, but is: #define. I tried > incluing go32.h but got errors (due to it being a C file I think). Yes. GNU Pascal does not parse C source. ;-) > How can I import _dos_ds? Only by re-writing the functionality of the macro (#define), i.e. translating it to Pascal. In this case it is access to a component of a struct (a record in Pascal): Type ByteInt = __byte__ Integer; (* 8 bit signed Integer *) Byte = __unsigned__ ByteInt; (* 8 bit unsigned Integer *) ShortInt = __short__ Integer; (* 16 bit signed Integer *) ShortWord = __unsigned__ ShortInt; (* 16 bit unsigned Integer *) (* Integer = __long__ Integer *) (* 32 bit signed Integer *) Word = __unsigned__ Integer; (* 32 bit unsigned Integer *) Go32InfoBlockRecord = record size_of_this_structure_in_bytes, linear_address_of_primary_screen, linear_address_of_secondary_screen, linear_address_of_transfer_buffer, size_of_transfer_buffer, (* >= 4k *) pid: Word; master_interrupt_controller_base, slave_interrupt_controller_base: Byte; selector_for_linear_memory: ShortWord; linear_address_of_stub_info_structure, linear_address_of_original_psp: Word; run_mode, run_mode_info: ShortWord; end (* Go32InfoBlockRecord *); Var Go32InfoBlock: asmname '_go32_info_block' Go32InfoBlockRecord; Then by typing Go32InfoBlock.selector_for_linear_memory you get the functionality of _dos_ds. Now, of course, you can define it as a macro (*$define _dos_ds Go32InfoBlock.selector_for_linear_memory *) but then the definition is case sensitive. Or: Write a C function which uses the macro, then use that function from Pascal. But that's less effective. Hope this helps, 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

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