- Gpc - gnu.de

--amtmpfile not given
by Jay Michael 15 Sep '13

15 Sep '13

On 11 Sep 2013 at 19:06, Stadelmann Josef wrote: > gpc: Internal GPC problem: internal option `--amtmpfile' not given > gpc1.exe: C:\dev_gpc\bin\gpc exited with status 1 > gpc1.exe: C:\dev_gpc\bin\gpc exited with status 1 Did you start using "gcc" instead of "gpc" to compile? Did you start using an uppercase extension on the source filename? Both of these produce "Internal GPC problem: internal option `--amtmpfile' not given". Neither of these produces any reference to gpc1.exe.

1 0

--amtmpfile not given
by Stadelmann Josef 12 Sep '13

12 Sep '13

what can I do in this case? it was compiling so nicely, and it was so fast, and then from one moment to the other, I don't know why, I get only one error. gpc: Internal GPC problem: internal option `--amtmpfile' not given gpc1.exe: C:\dev_gpc\bin\gpc exited with status 1 gpc1.exe: C:\dev_gpc\bin\gpc exited with status 1 exiting from Dev+GPC and ree-ntering the project is a no go either. the button: Build all AND the button: make project both buttons deliver the same error message. what can I do. Josef

2 1

Minimum Stack Size
by Kevan Hashemi 29 Jul '13

29 Jul '13

Dear GPC Users, I'm trying to force the operating system to give my Pascal code a 2-MByte stack so I can solve a problem with a recursive routine. I have tried: const {for recursive routines} minstacksize: cardinal = 2000000; attribute (name = '_stklen'); But that does not appear to work. Perhaps I am not trying hard enough. Am I on the right track? Yours, Kevan -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/

5 11

GPC for MinGW?
by Robert Hartmann 24 Jul '13

24 Jul '13

Hi list, If it is possible to integrate GPC into an actual MinGW-based GCC4 port, I like to get some hint. I would like to build in Msys (Windows XP), but if it easyer to build under Linux, well then I hope I could do it with Knoppix-Live-DVD. Best regards, Robert

3 3

64-Bit Compiler
by Kevan Hashemi 30 Jun '13

30 Jun '13

Dear GPC Maintainers, Is it possible to compile GPC from its existing sources to create a 64-bit Pascal compiler? I am vague on the back-end details of GPC, but it seems to me we would need a 64-bit version of GCC. My objective is to produce compiled code that will run on a 64-bit Scientific Linux machine that has no 32-bit libraries installed (I know this is an artificial situation, but the IT people at the international laboratory we work with are fond of artificial situations). Yours, Kevan -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/

3 3

Re: variable type cast
by Jay Michael 17 May '13

17 May '13

Adriaan van Os wrote: > > Jay Michael wrote: >> >> gpc version 20070904, based on gcc-3.4.5 (mingw special) >> Given >> type INT16 = INTEGER attribute( size=16 ) ; >> type WORD16 = Cardinal attribute( size=16 ) ; >> var i16 : INT16 ; >> var w16 : WORD16 ; >> why does >> WORD16(I16) := W16 ; >> produce "error: invalid lvalue in assignment"? > > A bug in the compiler. GPC is too picky when it comes to typecasts. Do you have any idea why this case is rejected? The compiler accepted type winbool = boolean attribute( size = 32 ) ; var i : integer ; var wb : winbool ; integer(wb) := 1024 ; integer(wb) := -1 ; integer(wb) := i ; I thought BOOLEAN was an enumeration type. I thought an enumeration type was a second cousin to an unsigned integer. So I thought the only real difference in my case was that I was using 16-bit integers. I was prepared for the compiler to accept the code and insist on generating range checks that I don't want. I'm just puzzled that it wouldn't even accept what looks to me to be just like examples I see posted of "variable type cast".

1 0

variable type cast
by Jay Michael 15 May '13

15 May '13

gpc version 20070904, based on gcc-3.4.5 (mingw special) Given type INT16 = INTEGER attribute( size=16 ) ; type WORD16 = Cardinal attribute( size=16 ) ; var i16 : INT16 ; var w16 : WORD16 ; why does WORD16(I16) := W16 ; produce "error: invalid lvalue in assignment"?

4 4

Fwd: Re: variable type cast
by Maurice Lombardi 13 May '13

13 May '13

-------- Message original -------- Sujet: Re: variable type cast Date : Mon, 13 May 2013 09:11:11 +0200 De : Maurice Lombardi <Maurice.Lombardi(a)ujf-grenoble.fr> Pour : Jay Michael <jmichael_ll(a)yahoo.com> Le 13/05/2013 01:12, Jay Michael a écrit : > gpc version 20070904, based on gcc-3.4.5 (mingw special) > Given > type INT16 = INTEGER attribute( size=16 ) ; > type WORD16 = Cardinal attribute( size=16 ) ; > var i16 : INT16 ; > var w16 : WORD16 ; > why does > WORD16(I16) := W16 ; > produce "error: invalid lvalue in assignment"? First notice tht the other way around I16 := INT16(W16) ; works. Typecasts are C style unportable "extensions" which garble the "write once, compile everywhere" philosophy behind the strong typing principles of Pascal. There is certainly nothing about it in the standards, and I do not know at which point this "lvalue error" crept in first into C, and then into Pascal. Maurice -- Maurice Lombardi Laboratoire Interdisciplinaire de Physique, (ex Spectrometrie Physique) Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 63 54 95 mailto:Maurice.Lombardi@ujf-grenoble.fr

1 0

for-loops and subrange types
by Jonas Maebe 29 Apr '13

29 Apr '13

Hi, Can anyone here offer some insights regarding the standard conformance of the test program submitted at http://bugs.freepascal.org/view.php?id=24318 ? (range.p) Both FPC and GPC cause the program to abort with a range check error, while the submitter is of the opinion that the for-loop should merely short-circuit and never executed instead. Jonas

5 10

Re: for-loops and subrange types
by Contestcen＠aol.com 27 Apr '13

27 Apr '13

This compatibility requirement seems to imply that the control variable need not be an integer type. Does this mean that Var letter: char; for letter := 'A' to 'Z' do is legitimate, or that the definers of the language expected that might eventually be allowed? Or does it merely mean that the magnitudes must match the range, so that Var num: smallint; for num := 20000 to 40000 do is illegal? In a message dated 4/26/2013 4:28:41 P.M. Eastern Daylight Time, jonas.maebe(a)elis.ugent.be writes: : The initial-value and the final-value of a sequence-iteration : of an iteration-clause of a for-statement shall be of a type : compatible with the type of control-variable of the for-statement. : The initial-value and the final-value shall be : assignment-compatible with the type possesed by the : control-variable if the statement of the for-statement : is executed.

2 1