- Gpc - gnu.de

Re: gpc installation support
by Adriaan van Os 23 Feb '10

23 Feb '10

kriti panday wrote: > HELLO > Please tell me how can i get support for gpc installation.To which mail > ID ,i will send my question. > Please support me.Tell me the procedure for GPC installation on Unix. More info here <http://alignment.hep.brandeis.edu/Software/Pascal/Index.html> Regards, Adriaan van Os

1 0

Hi everyone - got a question about GPC
by Hodges, Robert CTR USAF AFMC 520 SMXS/MXDEC 18 Feb '10

18 Feb '10

I downloaded GPC from this web site: http://www.gnu-pascal.de/binary/ I downloaded the binary version of GPC and GCC bundled together in RMP format for Linux. I specifically need GPC 2.1 with GCC 2.95, the file called gpc-2.1-with-gcc.i686-pc-linux-gnu.tar.gz <http://www.gnu-pascal.de/binary/gpc-2.1-with-gcc.i686-pc-linux-gnu.tar.gz> . I was greatly relieved to find this web site, and that binaries were available in the versions I needed. Problem is, when I install the RPM, it looks like the "binary" GCC compiler is incomplete - no actual binaries, compiler not ready to run. I could be wrong, so if I am, I need someone to help point me in the right direction. I'm a sysadmin who's installing this software for a developer, which I am not. Since I personally think the most ridiculous thing in the world is a compiler that won't work until it's compiled by another compiler, can anybody point me in the right direction to either an installable package of GPC 2.1, GCC 2.95 for Linux or tell me how to get this particular backage to work? Oh, I am attempting to install and run this package on SuSE Linux Enterprise Server 11. Major thanks in advance to anyone that can help out. Not sure what to think, the most recent update I can identify on the above web site was 5 years ago. Anybody out there? Bob

6 16

Re: Zeichensalat
by Adriaan van Os 17 Feb '10

17 Feb '10

egbert(a)seibertz.de wrote: > Moin Pascaller, > > im Rahmen von systemweiten Zeichensatzumstellungen (von > latin1 auf utf8) funktionieren nun erwartungsgemäß einige > Pascalprogramme nicht mehr. Teilweise weil Dateinamen > nicht mehr verstanden werden und teilweise weil Eingaben > nicht mehr verstanden werden. Oder die Nutzer die Ausgaben > nur noch erraten können ... > > Sehr ärgerlich an utf8 ist, daß durch die variable > Zeichenlänge der Programmieraufwand für die Erkennung > überproportional ansteigt. Möglicher Weise wäre utf16 > (USC2) deutlich einfacher im Aufwand ... Nach meiner Meinung ist UTF-16 wohl die slechteste Wahl, weil auch UTF-16 eine Kodierung ist mit variabeler Länge (<http://en.wikipedia.org/wiki/Utf-16>), obwohl Sie oft nicht als Solches behandelt wird, was dann wiederum zu Fehlern führt ! Ich bevorzuge UTF-8. Adriaan van Os

1 0

GPC support for AIX 6?
by Gert Doering 16 Feb '10

16 Feb '10

Hi Gnu Pascal list, we're currently using IBM's xpc pascal compiler on IBM AIX 5.3. New machines are being shipped with AIX 6, and IBM's xpc is no longer supported there - for the time being, it actuall works (the xpc frontend generated intermediate code, and the second stage compiler still groks it). Management is not happy about this, as it might break any day, and I have been asked to "provide GPC" on AIX 6. Googling seems to suggest that the earliest release of GCC to work on AIX 6 is gcc 4.2.4 This mailing list's archive suggests that GPC and GCC 4.2 do not yet work together, due to larger efforts required due to backend changes (Waldek's mail from March 12, 2008). I reported this to management ("there is no GPC on AIX 6"), and they came back with the question "if we pay one of the GPC developers to do a GPC port to a recent GCC, to support AIX 6, how much would that cost?". Here we go - I'm posing this question to you. Is one of you capable and willing to make GPC work on AIX 6? And if yes, what would your conditions be (estimated time to do this, estimated costs)? (I can't promise anything, but will report back to management and they will decide...) thanks, gert -- Gert Doering gd(a)medat.de MEDAT Muenchen Tel: 089/126808-0 Fax: -50

7 13

Long String Generation
by Kevan Hashemi 16 Feb '10

16 Feb '10

Dear GPC Users, I use long strings to pass numerical data into and out of a shared library I compile from Pascal. Right now, I generate a long string of numbers like this. program string_demo; var long_string:string(100000); i:integer; begin long_string:=''; for i:=1 to 10000 do writestr(long_string,long_string,i:1,' '); end. Clearly, this is inefficient. It takes 200 ms on my machine. If I use an array of characters instead of a string, and append each new entry to the array, execution time drops to 10 ms. I can't see a way of using GPC's writestr, concat, or trim functions to accelerate my string generation. I can't alter the long_string.length field directly. If I could fill up the string with spaces first, I could use the string as an array, then trim the spaces off the end. But filling up the string with spaces requires multiple calls to writestr, so I'm back where I started. It seems to me that I'm missing an obvious solution to my problem, and I thought you might point it out to me. Yours, Kevan -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/

4 6

compiler directives should be shut off when using --standard-pascal
by Rugxulo 03 Feb '10

03 Feb '10

Hi, I agree. This basically means that cmdline dialect options should take precedence over any listed in the file itself. This should not cause anybody much trouble, if any, except in some rare makefiles, and even that should be an easy fix. ---------- Forwarded message ---------- From: Scott Moore Date: Tue, Feb 2, 2010 at 1:38 PM Subject: Re: New P5 available To: Rugxulo In retrospect, it's probably not a good idea that GPC tries to take compiler directives from the programs. There should be a way to turn off GPC's parse of the compiler directives, since that would make GPC defacto non-standard. It should have been shut off with the --standard-pascal switch.

1 0

CWSDPMI r7 - 4GB support (Beta Test)
by Rugxulo 14 Jan '10

14 Jan '10

Charles Sandmann writes: "I would like to announce the beta for CWSDPMI release 7. The purpose of this release is to allow high performance access to large amounts of physical memory (up to 4GB). Memory above 32-bit address space (common on machines over 3GB physical memory) will be mapped to fill the address hole to provide a full 4GB memory. 4MB pages will be automatically used for large memory requests. Release 7 also includes the bug fixes included in the release 5 2008 refresh, and improved 4MB page support included in the never completed r6. Current DJGPP releases support large memory allocation requests and with CWSDPMI release 7 allow a contiguous memory block over 4091MB. This CWSDPMI release is dedicated to those few dozen people who want to prove their 4GB+ computers can actually run 4GB 32-bit applications. For those who need more than 4GB, I'll provide some code that allows you to map 5GB+ memory (up to 64GB) into the address space on request. The next release will probably be when I get several people bugging me that 64GB isn't enough under DOS :-) Binary Distribution: http://clio.rice.edu/djgpp/beta/csdpmi7b.zip Source Distribution: http://clio.rice.edu/djgpp/beta/csdpmi7s.zip Please send me any comments or bug reports. Have fun, and thanks for testing !"

1 0

Unable to print
by Contestcen＠aol.com 21 Dec '09

21 Dec '09

I tried that statement, but it did not recognize the command "net". Also the Pascal program seems to bomb when I use any value other than 'USB001' in the call to InitPrinter (or when I omit InitPrinter). The printer is connected directly to my computer by a USB cable. There is no local net. Date: Thurs, Dec 17 2009 5:00 am From: "Zaphod Beeblebrox" "SirJohn" <contestcen(a)aol.com> wrote in message news:dff19abd-9e4d-40c0-a4cb-d7aa8b66e7a3@j14g2000yqm.googlegroups.com... >I just moved to Windows 7, which means that I now connect to my > printer via a USB port instead of a serial port. In those FPC > programs which use the printer I changed InitPrinter('LPT1') to > InitPrinter('USB001') however, everything I print is now going to a > disk file named USB001 instead of to the printer. What else do I > need > to get this working? Make sure the printer is shared, and then use the following command to redirect LPT2 to the printer: net use LPT2: \\computername\printername /persistent:yes Replace 'computername' with your computer name, and 'printername' with the share name of your printer. After you've run the command, you should be able to use InitPrinter('LPT2') in your program. BTW, you want to use LPT2 since from what I've read, if the printer port actually exists, Vista and Windows 7 won't let you redirect to it. Hope this helps.

1 0

Unable to print
by Contestcen＠aol.com 21 Dec '09

21 Dec '09

I am using FPC 2.2.4 for i386. From: Marco van de Voort On 2009-12-17, SirJohn <contestcen(a)aol.com> wrote: > I just moved to Windows 7, which means that I now connect to my > printer via a USB port instead of a serial port. In those FPC > programs which use the printer I changed InitPrinter('LPT1') to > InitPrinter('USB001') however, everything I print is now going to a > disk file named USB001 instead of to the printer. What else do I need > to get this working? Which FPC are you using on windows 7? Could be one of the following three editions: go32v2/win32/win64 ? Note that go32v2(dos) is not supported/recommended on NT based windowses (NT4/2k/2k3/xp/vista/w2k8/w7).

1 0

Compiler differences
by John Gordon Ollason 11 Dec '09

11 Dec '09

Greetings, Having installed gpc 20060325, based on gcc-3.4.4 in replacement of gpc 20041218, based on gcc-3.3.3 I discovered that some programs which worked on the earlier version don't work on the later one. I narrowed the problem down to changes in the behaviour of goto. program gototest; label 9999; procedure try; begin goto 9999; end; { try } begin try; 9999: end. The program gototest.p is compiled by both compilers. The following program gototest1; label 9999; procedure try; begin goto 9999; end; { try } begin repeat try; 9999: until 0=0; end. is compiled by gpc 20041218 but the newer compiler gives the following error: gpc --classic-pascal gototest.p gototest.p: In main program: gototest.p:10: error: invalid target for nonlocal `goto' I have had a look at the ISO7185 specification, and though I am not an expert in these matters, it seems to me that the newer compiler is behaving incorrectly. Incidentally FreePascal gives the following error for both programs: Free Pascal Compiler version 2.2.2 [2008/10/26] for x86_64 Copyright (c) 1993-2008 by Florian Klaempfl Target OS: Linux for x86-64 Compiling gototest.p gototest.p(5,13) Error: Goto statements aren't allowed between different procedures gototest.p(14) Fatal: There were 1 errors compiling module, stopping Fatal: Compilation aborted Error: /usr/bin/ppcx64 returned an error exitcode (normal if you did not specify a source file to be compiled) Are any of the compilers behaving as specified in the ISO7815 standard? Best wishes, John O.

2 2