Gpc

gpc@gnu.de

5400 discussions

Possible bug in `ReadStr'/`Val'
by Frank Heckenbach 07 Feb '06

07 Feb '06

I noticed an incorrect handling of string parameters in a few RTS routines which might cause incorrect results when reading from strings where the actual parameters are expressions (not simple variables). `ReadStr' and `Val' might be affected, though I haven't been able to reproduce an actual problem. The rarely used `StringTFDD_Reset' is affected, that's where I found the problem. (fjf1099.pas) The attached patch fixes the bugs. For `StringTFDD_Reset', this results in an interface change, though for most uses it should be compatible (string -> conformant array of char), as long as the actual parameter is not an empty string. You'll have to rebuild the RTS and your units. You can do `make pascal.update-release' in the build gcc subdirectory before making GPC, to force GPC to recompile things. (I'm not including a version change in the patch, as the patch might be useable against several releases this way, though I've tested it only against one.) Waldek, you told me you're going to release a new snapshot soon. Please test this patch with your current code and include it if possible. Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: ACB3 79B2 7EB2 B7A7 EFDE D101 CD02 4C9D 0FE0 E5E8

2 6

External directives
by Prof A Olowofoyeku (The African Chief) 04 Feb '06

04 Feb '06

Hi If you have something like this: function foo : integer; external 'bar' name 'foo'; you get a warning that the library name in 'external' is ignored. Is it possible, instead of ignoring the library name, to generate an implicit call to link it? For example, the example above would resolve to an implicit '-lbar' (i.e., it would be the equivalent of '{$l bar}'). Is this feasible, and is there any reason why it would be a bad idea? BTW: this causes a compiler error: const barlib = 'bar'; function foo : integer; external barlib name 'foo'; Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/

3 3

crt & ncurses
by Russell Whitaker 04 Feb '06

04 Feb '06

Hi Some time ago I complained about getting grafic characters instead of f thru z, etc., when ncurses updated from 5.3 to 5.4 Since then I discovered if I insert SetPCCharSet( false ) before the first write the problem goes away. The following program illistrates it: program ncur; uses CRT; begin if( GetPCCharSet ) then begin writeln("true"); SetPCCharSet( false ); writeln("true"); end else writeln("false"); end. Russ

3 4

Ada calling Pascal (not working)
by lanceboyle＠qwest.net 03 Feb '06

03 Feb '06

(This post is related to two earlier posts by me, "Linking Ada to Pascal" and 'Where is documentation for "new argument to _p_initialize (@)" PCStrings.') I have not been able to solve the problem when calling _p_initialize from Ada. I still get the Ada compiler telling me, "too many arguments in call." I suspect that I might be passing the wrong _kinds_ of arguments but not the wrong number. Here are the three relevant files: <file adacallspascal.adb> with Ada.Text_IO; use Ada.Text_IO; with Ada.Command_Line; use Ada.Command_Line; with Ada.Integer_Text_IO; use Ada.Integer_Text_IO; procedure adacallspascal is procedure mypascalprocedure; pragma Import(Convention => C, Entity => mypascalprocedure); procedure init_pascal_main_program; pragma Import(Convention => C, Entity => init_pascal_main_program, External_Name => "_p__M0_init"); procedure p_initialize; pragma Import(Convention => C, Entity => p_initialize, External_Name => "_p_initialize"); procedure p_finalize; pragma Import(Convention => C, Entity => p_finalize, External_Name => "_p_finalize"); Argument_Count_Plus_1 : integer := Argument_Count + 1; Command_Name_String : string := Command_Name; C_Command_Name_String : aliased string := Command_Name_String & ASCII.NUL; begin Put_Line ("Hello from adacallspascal."); Put(Argument_Count_Plus_1); New_Line; Put_Line(Command_Name_String); -- Initialize the Pascal RTS. p_initialize (Argument_Count_Plus_1, C_Command_Name_String'access, null, 0); -- Line 29 init_pascal_main_program; mypascalprocedure; p_finalize; Put_Line ("Goodbye from adacallspascal."); end adacallspascal; <file mypascalprogram.pas> program mypascalprogram(input, output); {$gpc-main=dummy} procedure mypascalprocedure; attribute( name = 'mypascalprocedure'); begin writeln('Hello from mypascalprocedure.'); end; begin {When exported to Ada, this part should not be called.} writeln('In mypascalprogram; error if calling from Ada.'); end. <The commands> gpc -c mypascalprogram.pas gnatmake adacallspascal.adb -gnatf -largs mypascalprogram.o / Developer/Pascal/gpc344d2/lib/gcc/powerpc-apple-darwin8/3.4.4/libgpc.a <Output from attempting to compile> gcc -c -gnatf adacallspascal.adb adacallspascal.adb:29:05: too many arguments in call gnatmake: "adacallspascal.adb" compilation error Jerry

4 4

Incompatible types error detection bug
by Gale Paeper 02 Feb '06

02 Feb '06

GPC fails to detect incompatible type errors between two or more new-pointer-type defined types where the same domain-type is used in new-type type-denoters. An example demonstrating the bug: {$extended-pascal} program grp12(output); type t1 = ^integer; t2 = ^integer; var x: t2; procedure foo(p: t1); begin end; begin foo(x); {WRONG - incompatible types} writeln('FAIL'); end. Although both t1 and t2's new-pointer-type type-denoter have the same domain-type, t1 and t2 are distinctly different types. Therefore, t1 and t2 aren't assignment-compatible types (per ISO 10206 paragraph 6.4.6) and the foo(x) call is illegal since the actual-parameter type (t2) isn't assignment-compatible with the formal-paramter type (t1) as required by ISO 10206 paragraph 6.7.3.2. The compiler I used was the latest version of Mac OS X GPC that Adriaan built and made available for downloading. The specs: Reading specs from /Developer/Pascal/gpc345u2/lib/gcc/powerpc-apple-darwin8/3.4.5/specs Configured with: ../gcc-3.4.5/configure --enable-languages=pascal,c --enable-threads=posix --target=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --build=powerpc-apple-darwin8 --prefix=/Developer/Pascal/gpc345u2 Thread model: posix gpc version 20051116, based on gcc-3.4.5 P.S. This bug was originally found by Mike Hore and discussed on the MacPascal mailing list. The above example is a distilled version of the problem he found while working with Mac OS X GPC and the Mac OS X GPCPInterfaces. Gale Paeper gpaeper(a)empirenet.com

3 2

Re: Getting an error while compiling GPC-20050331 on HP-UX11i v2
by prasad svr 02 Feb '06

02 Feb '06

Hi, I tried with gpc-20051116 on HP-UX11i v2 (Itanium),i am geeting an error like ocal/ia64-hp-hpux11.23/include -isystem /usr/local/ia64-hp-hpux11.23/sys-include' ' | sed -e 's,$-[BI]$$[^/][^:]$,\1../../\2,g;s,^$[^/][^:]*/$,../../\1,'`" PC="`echo ./xgpc -B./' ' | sed -e 's,$-[BI]$$[^/][^:]$,\1../../\2,g;s,^$[^/][^:]*/$,../../\1,'`" GCC_VERSION="3.4.3" SHELL="/bin/sh" CFLAGS="-g -O2" PFLAGS="" AR_FLAGS="rc" RTSFLAGS="" DESTDIR="../.." AR="ar" RANLIB="ranlib" RANLIB_TEST="" all make[2]: Entering directory `/gcc/gpcbuild/gcc/p/rts' echo '{ rts-config.inc. Generated automatically from rts-config.h. }' > rts-config.inc sed -e 's,/\*,{,g;s,\*/,},g;s,^[ \t]*#$.*$,{$\1},' rts-config.h >> rts-config.inc ../.././xgpc -B../.././ -I. -W -Wall -Wmissing-prototypes -Wmissing-declarations -g -O2 --unit-path=/gcc/gcc-3.4.3/gcc/p/rts --automake --print-needed-options "/gcc/gcc-3.4.3/gcc/p/rts/endian.pas" 2> "needed-options" || true if grep '^[^-]' "needed-options" > /dev/null; then echo "needed-options: `cat "needed-options"`" >&2; rm -f "needed-options"; false; else true; fi needed-options: /gcc/gcc-3.4.3/gcc/p/rts/endian.pas:37: error: module/unit interface `Error' could not be imported make[2]: *** [needed-options] Error 1 make[2]: Leaving directory `/gcc/gpcbuild/gcc/p/rts' make[1]: *** [pascal.rts] Error 2 make[1]: Leaving directory `/gcc/gpcbuild/gcc' make: *** [all-gcc] Error 2 can any one help on this. Regards Prasad > ----- Original Message ----- > From: "Waldek Hebisch" <hebisch(a)math.uni.wroc.pl> > To: gpc(a)gnu.de > Subject: Re: Getting an error while compiling GPC-20050331 on HP-UX11i v2 (Itanium > Date: Fri, 27 Jan 2006 15:53:27 +0100 (CET) > > > prasad svr wrote: > > I am trying to compile GPC-20050331 on HP-UX11i v2 (Itanium 64 > > bit) Using gcc-3.4.3.While compiling Iam getting an error like > > bellow. > > > > > > gcc ?c -DUSE_LIBUNWIND_EXCEPTIONS -g -O2 -DIN_GCC -W -Wall > > -Wwrite-string -Wstrict-prototypes -Wmissing -Prototypes > > -pedantic -Wno-long-long -DHAVE_CONFIG_H > > -DGENERATOT_FILE -I. ?I. > > > > -I/gcc/gcc-3.4.3/gcc -I/gcc/gcc-3.4.3/gcc/. > > ?I/gcc/gcc-3.4.3/gcc/../include -I ../intl > > /gcc/gcc-3.4.3/gcc/gcov-iov.c -o gcov-iov.o > > > > In file included from /gcc/gcc-3.4.3/gcc/gcov-iov.c: 27: > > > > /gcc/gcc-3.4.3/gcc/version.c: 8 error: Conflicting type for `version string' > > /gcc/gcc-3.4.3/gcc/version.h: 3 error: previous declaration of > > `version string' was here > > /gcc/gcc-3.4.3/gcc/version.c: 8 error: conflicting types for `version string' > > /gcc/gcc-3.4.3/gcc/version.h: 3 error: previous declaration of > > `version string' was here > > > > First suspect is incorrectly patched backend: gpc contains a patch which > modifies both `version.c' and `version.h'. If only one of them is patched > you will get errors as above. > > gpc-20050331 is likely to have problems on IA-64, but the above is _not_ > one of expected problems. To avoid other problems I would suggerst > to use gpc-20051116 version from: > > http://www.math.uni.wroc.pl/~hebisch/gpc/gpc-20051116.tar.bz2 > > or search the mailing list archives for patches. > > -- > Waldek Hebisch > hebisch(a)math.uni.wroc.pl > -- _______________________________________________ Search for businesses by name, location, or phone number. -Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.as…

2 1

Buffer Overrun Prevention in GPC
by Mirsad Todorovac 30 Jan '06

30 Jan '06

Hi, all! I have recently studied several forms of viruses and security holes in software. Many if not 90% of recent exploits depend on holes introduced through buffer overruns, such as this C example: printbuffer() { char buffer[100]; gets (buffer); /* oops!*/ fp = fopen("LPT1:", "w"); fputs (buffer, fp); } Is Pascal and namely GNU Pascal safer re: buffer overruns? How much does runtime range checking help and to what extent can we depend on it? Is it acceptable to write setuid root programs in GPC and what are the cautions? Thanks for answers. Mirsad "Tvrdim da bi se napetost izmedju znanosti i vjere trebala rijesiti njihovom sintezom, a ne odbacivanjem ili podvojenoscu." Pierre Teilhard de Chardin (1881-1955)

3 18

Internal compiler error with readstring
by Peter Schorn 28 Jan '06

28 Jan '06

The following program crashes the compiler (gpc345u2 on Mac OS 10.4.4): program rs; { compile with gpc rs.pas } var a: integer; begin readstring(a); { internal compiler error: Bus error } end. Best regards, Peter

5 8

Getting an error while compiling GPC-20050331 on HP-UX11i v2 (Itanium 64 bit) using gcc-3.4.3.
by prasad svr 27 Jan '06

27 Jan '06

Hi, I am trying to compile GPC-20050331 on HP-UX11i v2 (Itanium 64 bit) Using gcc-3.4.3.While compiling Iam getting an error like bellow. gcc c -DUSE_LIBUNWIND_EXCEPTIONS -g -O2 -DIN_GCC -W -Wall -Wwrite-string -Wstrict-prototypes -Wmissing -Prototypes -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOT_FILE -I. I. -I/gcc/gcc-3.4.3/gcc -I/gcc/gcc-3.4.3/gcc/. I/gcc/gcc-3.4.3/gcc/../include -I ../intl /gcc/gcc-3.4.3/gcc/gcov-iov.c -o gcov-iov.o In file included from /gcc/gcc-3.4.3/gcc/gcov-iov.c: 27: /gcc/gcc-3.4.3/gcc/version.c: 8 error: Conflicting type for `version string' /gcc/gcc-3.4.3/gcc/version.h: 3 error: previous declaration of `version string' was here /gcc/gcc-3.4.3/gcc/version.c: 8 error: conflicting types for `version string' /gcc/gcc-3.4.3/gcc/version.h: 3 error: previous declaration of `version string' was here make[1]: *** [gcov-iov.o] Error 1 make[1]: Leaving directory `/gcc/gpcbuild/gcc' make: *** [all-gcc] Error 2 any one can help on this problem. Regards Prasad -- _______________________________________________ Search for businesses by name, location, or phone number. -Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.as…

3 2

MinGW -mwindows -mconsole
by Adriaan van Os 25 Jan '06

25 Jan '06

Has somebody worked with gpc on MinGW passing both -mwindows and -mconsole to create both a console box and GUI stuff ? Is a different thread needed for the GUI ? Regards, Adriaan van Os

3 5

Jump to page:

2025

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