Gpc June 1998

gpc@gnu.de

38 participants
59 discussions

Some GPC bugs
by Marius Gedminas 22 Jun '98

22 Jun '98

Hi, developers! I have successfully downloaded and compiled GPC-980511 for Linux. There still are two problems with the makefile: 1. Subdirectory /p in the gcc source directory may not be a symlink (make finds out the real directory and complains about missing `../configure') - I remember I've seen this problem reported together with a patch on the list. 2. Compiling the RTL for the first time fails because `gpc' is not found (it is still called `xgpc' at the moment) However I was unable to install RHIDE for Linux (rpm2tgz from Slackware 3.4 distribution fails with the rpm package) so I used DJGPP version to examine the following bugs: 1. GPC preprocessor outputs too many empty lines when removing text between {$IFDEF} ... {$ENDIF}. A sample program: {1} program LineNumberBug; {2} {3} {$IFDEF NotDefined} {4} This line is not compiled {5} {$ENDIF} {6} {7} begin {8} ! { Generate syntax error on line 8 } {9} end. ...>gpc main.pas main.pas: In function `program_Linenumberbug': main.pas:11: parse error before `!' ^^ should be 8 2. Procedural variables are always passed by value. program ProcBug; type TProc = procedure; procedure NoBug(X: TProc); begin { X is passed by value as it should be } end; procedure Bug(var X: TProc); begin { X is passed by value here too! } { If I tried to modify X, I would corrupt code of some procedure } end; var Tmp: TProc; begin NoBug(Tmp); { These two calls in .S file are identical } Bug(Tmp); end. 3. (I think this one is not new) `--automake' does pass all required .o files to the linker if it didn't need to recompile the sources. (Windows 95 crashed as usual and I had to retype everything from scratch. I should once again try to install RHIDE for Linux...) Yours, -- Marius Gedminas "A Hacker is any person who derives E-mail: mgedmin(a)pub.osf.lt joy from discovering ways to WWW: http://www-public.osf.lt/~mgedmin/ circumvent limitations." rab'86

2 3

UNSUBCRIBE
by moriaud＠drfmc.ceng.cea.fr 22 Jun '98

22 Jun '98

PLEASE UNSUBCRIBE ME FROM THIS MAILING LIST

1 0

No crt0.o with cygwin32 version
by Hans Lunsing 21 Jun '98

21 Jun '98

Hi, 1. I installed GNU Pascal for Cygwin32. When I try to compile and link a pascal source file I get the message ld.exe: cannot open crt0.o: No such file or directory (ENOENT) I know crt0.o contains the startup code for C. Where can I find that file, and if found, where do I place it so that the linker can find it? 2. I tried to run the Makefile for the borland pascal extensions with GNU Make 3.75 for DJGPP V2. It gave an error message: for x in head.pas nohead.pas cstparam.pas caseelse.pas switches.pas bitmanip.pas incdec.pas minimax.pas mem.pas abso.pas asmnames.pas openarr.pas varrec.pas voidparm.pas ; do \ rm -f a.out 2>/dev/null ; \ gpc -g -O3 --automake="-g -O3" $x 2>/dev/null ; \ echo -n "$x: " ; \ if [ -f "a.out" ] ; then ./a.out ; else echo "failed" ; fi ; \ done ; \ rm myunit.o myunit.gpi a.out 2>/dev/null ; Command line too long. make.exe: *** [bptest] Error -1 So I wonder, is this the right version of Make to use? 3. I also installed GNU Pascal for DJGPP version 2. That works fine (till now)! Hans Lunsing e-mail: jlunsing(a)doge.nl

3 2

GPC 2.1 for EGCS 1.1?
by Peter Gerwinski 19 Jun '98

19 Jun '98

Hello, Jeff! Hello, all! (I am citing everything, so the GPC list members know what we are talking about without browsing the HTML page.) On Wed, 17 Jun 1998 22:46:37 -0600, Jeffrey A Law (law(a)cygnus.com) wrote in http://www.cygnus.com/ml/egcs/1998-Jun/0628.html: > > egcs-1.1 > > The egcs project is rapidly approaching its second major release > (egcs-1.1). > > This page is meant to provide information about the current schedule > for egcs-1.1, the testing/release criteria for egcs-1.1, new features > to be found in egcs-1.1, etc. Maybe this schedule is also reasonable for the next mejor release of GPC (gpc-2.1). I don't know how realistic this is, but the list of bug reports for the latest alpha release was much shorter than for previous ones. It is probably not reasonable to try to integrate the BP compatibility package and other independent contributions (such as GRX) into the GPC distribution by this date, so let's keep them independent. > The tenative schedule for the egcs-1.1 release is: > * July 3, 1998. Feature freeze date. > All new features, optimizations, etc need to be submitted by this > date. It is very likely we will not be able to integrate all the > submissions, but we want to have all of them available for > evaluation by this date. > It is also possible some patches which have been submitted and are > accepted for egcs-1.1 will not have been installed by this date > due to EOQ committments for many of the Cygnus volunteers. > After July 3, 1998, only bugfix submissions will be considered for > the egcs-1.1 release. > By July 3, 1998, we also want to have a testing plan and release > criteria in place. For GPC this means that all scheduled features (e.g. some filled BP holes) have to be in place by that date. This merely concerns my own work. I will try to compose a new :-) beta (-: GPC snapshot by this weekend. > * July 11, 1998. Branch Creation & Testing. > We will create the egcs-1.1 branch on this date and snapshots will > occur from the egcs-1.1 branch instead of the mainline sources. > By this date we'd like to have all the new features, > optimizations, etc slated for the egcs-1.1 release installed in > the source tree. > We also expect wide scale, focused testing to start on July 11th. It would be desirable to release updated versions of BPcompat etc. together with gpc-2.1 (while in a separate package). In order to make this possible, gpc-980711 must be about the final version of gpc-2.1. > * July 31, 1998. Critial Bug Freeze Date. > If at all possible we would like to see the release sources freeze > except for critical bug fixes by July 31st. This may be overly > optimistic, but it's important to have a goal to shoot for. Besides the actual work on GPC, this means that all administrative tasks (copyright assignments etc.) must be finished before August. Those of you who are considering to contribute to the GPC compiler itself should contact me NOW so we have a chance to get these jobs done in time. (It involves papers that have to fly over the Atlantic!) > I would like to release as soon as possible in early August. > > Note that we have the ability to install changes into the mainline > sources during this process. However, I personally will be focusing > more and more on egcs-1.1 specific issues. > > It is highly likely we will have some minor releases based on > egcs-1.1; we will cross that bridge when the time comes. For GPC, we are planning to split the development into a "stable" line (gpc-2.1.x) and an "experimental" one (gpc-1998mmdd) in order to avoid long delays between the releases (about sqrt(3) years in this case)-: to happen again. > I also want to do a post-release review of the proposed schedule vs > the actual schedule used for egcs-1.1 so that we can improve the > process in the future. > > This message (and future updates) is available on > http://www.cygnus.com/egcs/egcs-1.1.html Greetings, Peter -- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-980511 PGP key on request - 6C 94 45 BE 28 A4 96 - 0E CC E9 12 47 25 82 75 Fight the SPAM and UBE! - http://spam.abuse.net/ - http://maps.vix.com/

3 3

GPC REF: do (texi)
by Miklos Cserzo 19 Jun '98

19 Jun '98

Hi Folks, here goes the "final" version. I am going to have a break for the next 3 weeks. More sections to come after that. miklos ___________________________ @c---------------------------------------------------------------------------- @node do @unnumberedsec do @cindex do @unnumberedsubsec Description The @samp{do} reserved word is used in combination with other Pascal keywords in many ways. For description and examples see the relevant reference sections: @samp{for}, @samp{while}, @samp{with}, @samp{to begin}, @samp{to end}. @unnumberedsubsec Standards @samp{do} is defined in the ISO-7185 Standard Pascal and supported by all known Pascal variants. @unnumberedsubsec See also @ref{for}, @ref{while}, @ref{with}, @ref{to begin}, @ref{to end}. @c----------------------------------------------------------------------------

1 0

subscribe
by Robert P. Ewing 18 Jun '98

18 Jun '98

Please subscribe me to the gpc mailing list.

1 0

None
by None 18 Jun '98

18 Jun '98

k by faui45.informatik.uni-erlangen.de (8.8.8/8.1.16-FAU) with ESMTP id PAA07137 for <heckenb(a)mi.uni-erlangen.de>; Thu, 18 Jun 1998 15:42:32 +0200 (MET DST) Received: from smtp3.erols.com (smtp3.erols.com [207.172.3.236]) by santra.hut.fi (8.9.0/8.9.0) with ESMTP id QAA27401 for <gpc(a)hut.fi>; Thu, 18 Jun 1998 16:25:12 +0300 (EET DST) Received: from icekool (207-172-110-153.s26.as3.frd.erols.com [207.172.110.153]) by smtp3.erols.com (8.8.8/8.8.5) with SMTP id JAA01871 for <gpc(a)hut.fi>; Thu, 18 Jun 1998 09:25:08 -0400 (EDT) From: "Billy Johnson" <icekool(a)erols.com> To: <gpc(a)hut.fi> Subject: unsubscribe Date: Thu, 18 Jun 1998 09:26:13 -0400 Message-ID: <01bd9abc$aa0f4ae0$996eaccf@icekool> MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01BD9A9B.22FDAAE0" Content-Length: 979 This is a multi-part message in MIME format. ------=_NextPart_000_000A_01BD9A9B.22FDAAE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Please, unsubscribe me from GPC mailing list.=20 Thanks for all. Billy Johnson ------=_NextPart_000_000A_01BD9A9B.22FDAAE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HTML> <HEAD> <META content=3Dtext/html;charset=3Diso-8859-1 = http-equiv=3DContent-Type> <META content=3D'"MSHTML 4.71.1712.3"' name=3DGENERATOR> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT color=3D#000000 size=3D2>Please, unsubscribe me from GPC = mailing list.=20 </FONT></DIV> <DIV><FONT color=3D#000000 size=3D2>Thanks for all.</FONT></DIV> <DIV><FONT color=3D#000000 size=3D2></FONT> </DIV> <DIV><FONT color=3D#000000 size=3D2>Billy = Johnson</FONT></DIV></BODY></HTML> ------=_NextPart_000_000A_01BD9A9B.22FDAAE0--

1 0

gpc-980511.i386-msdos-djgpp bug
by Marius Gedminas 18 Jun '98

18 Jun '98

Hi, developers! This is not urgent but should be fixed before the release goes out. GPC-980511 for DJGPP crashes if the DJGPP variable is set incorrectly (In my case it was set to C:\DJGPP instead of C:\DJGPP\DJGPP.ENV). This happens only if there are some arguments on the command line: ...>gpc --verbose Exiting due to signal SIGSEGV Page fault at eip=0000f0a5, error=0006 eax=00064924 ebx=00000013 ecx=00010000 edx=0000f109 esi=00000000 edi=00000000 ebp=00064928 esp=00064914 program=C:\DJGPP\BIN/gpc.exe cs: sel=00e7 base=10060000 limit=0142ffff ds: sel=00ef base=10060000 limit=0142ffff es: sel=00ef base=10060000 limit=0142ffff fs: sel=00cf base=00020270 limit=0000ffff gs: sel=00ff base=00000000 limit=ffffffff ss: sel=00ef base=10060000 limit=0142ffff Call frame traceback EIPs: 0x0000f0a5 0x0000f251 0x0000f2f5 0x00006b47 0x00008afe 0x0000d0eb 0x00010592 And sometimes the PC hangs after this. This was plain MS-DOS 7.10 with CWSDPMI V0.90+ (r3). Another question: gpc-980511.i386-pc-msdos-djgpp.zip contains a different LIBGCC.A than gcc281b.zip - should it be so? gpc-980511.i386-pc-msdos-djgpp.zip: libgcc.a 332,018 1998 Mar 29 21:26 gcc281b.zip: libgcc.a 282,626 1998 Jun 06 13:47 Besides, gpc-980511.i386-pc-msdos-djgpp.zip does not contain crtf.o. Yours, -- Marius Gedminas "A Hacker is any person who derives E-mail: mgedmin(a)pub.osf.lt joy from discovering ways to WWW: http://www-public.osf.lt/~mgedmin/ circumvent limitations." rab'86

1 0

unsubscribe me please
by Tano Fotang 17 Jun '98

17 Jun '98

would someone help me get off the list for now? holiday time.. /tano -- Genius doesn't work on an assembly line basis. You can't simply say, "Today I will be brilliant." -- Kirk, "The Ultimate Computer", stardate 4731.3

1 0

None
by Dr Montaz Ali 17 Jun '98

17 Jun '98

Please include me in the user group

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