Gpc

gpc@gnu.de

5400 discussions

instal gnu pascal
by Palmerim Soares 23 Feb '09

23 Feb '09

Help! I use Windows XP. I just want to instal and use GNU pascal but it seens to be very very very difficult!!!!!! What i have to do to simply instal and use GNU Pascal without guesses and a lot of complications????????????? Thanks for your help Palmerim

2 1

With statement behaviour for objects
by Adriaan van Os 21 Feb '09

21 Feb '09

Any comments on <http://bugs.freepascal.org/view.php?id=13210> ? Regards, Adriaan van Os

3 2

GNU Pascal and warnings.
by Lennart Thelander 19 Feb '09

19 Feb '09

Hello. For quite many functions/Procedures, I get two warnings: warning: frame size too large for reliable stack checking warning: try reducing the number of local variables Say what? Reducing the number of local variables? Here's an example: PROCEDURE TTextEditItem.HandleKey(VAR theEvent:EventRecord); VAR i : SInt16; pt : Point; theChr : Char; theKey : SInt16; shift : BOOLEAN; option : BOOLEAN; control : … [View More]

3 3

[Commit] gdb/pascal language 2 or 4 byte char support in strings
by Pierre Muller 10 Feb '09

10 Feb '09

I committed the patch below to add support for fixed width chars greater than 1 for pascal language. This works nicely for Free Pascal, I couldn't test it for GPC because I didn't find out if those kind of char are supported... Pierre Muller Pascal language support maintainer for GDB ChangeLog entry: 2009-02-08 Pierre Muller <muller(a)ics.u-strasbg.fr> * p-lang.c (is_pascal_string_type): Fix comment. Determine exact size of char elements for GPC strings. (pascal_printstr):… [View More] Handle char width of 2 or 4. * p-valprint.c (pascal_val_print): Handle char of width 2 or 4. Index: gdb/p-lang.c =================================================================== RCS file: /cvs/src/src/gdb/p-lang.c,v retrieving revision 1.45 diff -u -p -r1.45 p-lang.c --- gdb/p-lang.c 5 Feb 2009 12:16:25 -0000 1.45 +++ gdb/p-lang.c 9 Feb 2009 23:54:58 -0000 @@ -86,7 +86,7 @@ pascal_main_name (void) } /* Determines if type TYPE is a pascal string type. - Returns 1 if the type is a known pascal type + Returns a positive value if the type is a known pascal string type. This function is used by p-valprint.c code to allow better string display. If it is a pascal string type, then it also sets info needed to get the length and the data of the string @@ -126,14 +126,20 @@ is_pascal_string_type (struct type *type && strcmp (TYPE_FIELDS (type)[0].name, "Capacity") == 0 && strcmp (TYPE_FIELDS (type)[1].name, "length") == 0) { - if (length_pos) + struct type *char_type; + if (length_pos) *length_pos = TYPE_FIELD_BITPOS (type, 1) / TARGET_CHAR_BIT; - if (length_size) + if (length_size) *length_size = TYPE_LENGTH (TYPE_FIELD_TYPE (type, 1)); - if (string_pos) + if (string_pos) *string_pos = TYPE_FIELD_BITPOS (type, 2) / TARGET_CHAR_BIT; /* FIXME: how can I detect wide chars in GPC ?? */ - if (char_size) + char_type = TYPE_FIELD_TYPE (type,2); + if (char_size && TYPE_CODE (char_type) == TYPE_CODE_ARRAY) + { + *char_size = TYPE_LENGTH (TYPE_TARGET_TYPE (char_type)); + } + else if (char_size) *char_size = 1; if (arrayname) *arrayname = TYPE_FIELDS (type)[2].name; @@ -218,7 +224,8 @@ pascal_printstr (struct ui_file *stream, /* If the string was not truncated due to `set print elements', and the last byte of it is a null, we don't print that, in traditional C style. */ - if ((!force_ellipses) && length > 0 && string[length - 1] == '\0') + if ((!force_ellipses) && length > 0 + && extract_unsigned_integer (string + (length - 1) * width, width) == 0) length--; if (length == 0) @@ -234,6 +241,7 @@ pascal_printstr (struct ui_file *stream, unsigned int rep1; /* Number of repetitions we have detected so far. */ unsigned int reps; + unsigned long int current_char; QUIT; @@ -243,9 +251,13 @@ pascal_printstr (struct ui_file *stream, need_comma = 0; } + current_char = extract_unsigned_integer (string + i * width, width); + rep1 = i + 1; reps = 1; - while (rep1 < length && string[rep1] == string[i]) + while (rep1 < length + && extract_unsigned_integer (string + rep1 * width, width) + == current_char) { ++rep1; ++reps; @@ -261,7 +273,7 @@ pascal_printstr (struct ui_file *stream, fputs_filtered ("', ", stream); in_quotes = 0; } - pascal_printchar (string[i], stream); + pascal_printchar (current_char, stream); fprintf_filtered (stream, " <repeats %u times>", reps); i = rep1 - 1; things_printed += options->repeat_count_threshold; @@ -269,8 +281,7 @@ pascal_printstr (struct ui_file *stream, } else { - int c = string[i]; - if ((!in_quotes) && (PRINT_LITERAL_FORM (c))) + if ((!in_quotes) && (PRINT_LITERAL_FORM (current_char))) { if (options->inspect_it) fputs_filtered ("\\'", stream); @@ -278,7 +289,7 @@ pascal_printstr (struct ui_file *stream, fputs_filtered ("'", stream); in_quotes = 1; } - pascal_one_char (c, stream, &in_quotes); + pascal_one_char (current_char, stream, &in_quotes); ++things_printed; } } Index: gdb/p-valprint.c =================================================================== RCS file: /cvs/src/src/gdb/p-valprint.c,v retrieving revision 1.59 diff -u -p -r1.59 p-valprint.c --- gdb/p-valprint.c 3 Jan 2009 05:57:52 -0000 1.59 +++ gdb/p-valprint.c 9 Feb 2009 23:54:58 -0000 @@ -79,7 +79,7 @@ pascal_val_print (struct type *type, con print_spaces_filtered (2 + 2 * recurse, stream); } /* For an array of chars, print with string syntax. */ - if (eltlen == 1 + if ((eltlen == 1 || eltlen == 2 || eltlen == 4) && ((TYPE_CODE (elttype) == TYPE_CODE_INT) || ((current_language->la_language == language_pascal) && (TYPE_CODE (elttype) == TYPE_CODE_CHAR))) @@ -93,14 +93,15 @@ pascal_val_print (struct type *type, con /* Look for a NULL char. */ for (temp_len = 0; - (valaddr + embedded_offset)[temp_len] + extract_unsigned_integer (valaddr + embedded_offset + + temp_len * eltlen, eltlen) && temp_len < len && temp_len < options->print_max; temp_len++); len = temp_len; } - LA_PRINT_STRING (stream, valaddr + embedded_offset, len, 1, 0, - options); + LA_PRINT_STRING (stream, valaddr + embedded_offset, len, + eltlen, 0, options); i = len; } else @@ -165,14 +166,17 @@ pascal_val_print (struct type *type, con /* For a pointer to char or unsigned char, also print the string pointed to, unless pointer is null. */ - if (TYPE_LENGTH (elttype) == 1 - && (TYPE_CODE (elttype) == TYPE_CODE_INT - || TYPE_CODE(elttype) == TYPE_CODE_CHAR) + if (((TYPE_LENGTH (elttype) == 1 + && (TYPE_CODE (elttype) == TYPE_CODE_INT + || TYPE_CODE (elttype) == TYPE_CODE_CHAR)) + || ((TYPE_LENGTH (elttype) == 2 || TYPE_LENGTH (elttype) == 4) + && TYPE_CODE (elttype) == TYPE_CODE_CHAR)) && (options->format == 0 || options->format == 's') && addr != 0) { /* no wide string yet */ - i = val_print_string (addr, -1, 1, stream, options); + i = val_print_string (addr, -1, TYPE_LENGTH (elttype), stream, + options); } /* also for pointers to pascal strings */ /* Note: this is Free Pascal specific: [View Less]

2 2

Re: Write doesn't work with CRT
by Alexey Kotlyarov 25 Jan '09

25 Jan '09

> Depending on what you want to do, > either > writeln("sqrt(-1)"); > or > writeln(sqrt(1)); > works. I'm sorry, I haven't made it clear the first time. So: With CRT, all writeln do nothing. For example: uses crt; begin writeln('OK') end. produces nothing. uses crt; begin writeln('OK'); writeln(sqrt(-1)) end. produces just the error message from sqrt(-1), NOT 'OK'. Same programs without "uses crt;" both include 'OK' (the latter before the error message). … [View More]

3 2

Write doesn't work with CRT
by Alexey Kotlyarov 25 Jan '09

25 Jan '09

Being compiled version of GPC installed on Ubuntu, the following very simple program fails to produce any output: program testcrt; uses crt; begin writeln('OK'); writeln(sqrt(-1)); { error } end. $ gpc --automake testcrt.pas -o testcrt $ ./testcrt ./testcrt: argument to `SqRt' is < 0 (error #708 at 40b6c6) Notice the absence of OK. Similarly, removing error line makes program produce no output. Removing 'uses crt;' restores normal behavior. Version info and such: $ gpc --version gpc … [View More]

3 5

LLVM
by Adriaan van Os 25 Jan '09

25 Jan '09

I would like to draw your all attention to the LLVM compiler infrastructure <http://llvm.org/>. I hear good things about it from people writing compiler front-ends for it. There is also the clang front-end <http://clang.llvm.org/> project. LLVM may in the future replace GCC in many software projects. It may be a good idea to get somehow involved. Regards, Adriaan van Os

1 0

X CODE 3.1 AND INTEGRATION PROBLEMS
by MICHAEL MCNEESE 21 Jan '09

21 Jan '09

I recently added GNU Pascal to my inventory of languages in X Code 3.1 along with the integration kit. Unfortunately, Pascal does not show up in the X Code enviroment. Its possible that upon installation the it simply is not indexed properly. Does anyone have any suggestions? mike

2 2

New version?
by leledumbo 06 Jan '09

06 Jan '09

Will there be any new version of gpc? Or at least the latest one (20070904) with gcc 4.2.X or 4.3.X integration? -- View this message in context: http://www.nabble.com/New-version--tp21308910p21308910.html Sent from the Gpc mailing list archive at Nabble.com.

1 0

Linux Binaries and Makefile
by Kevan Hashemi 01 Jan '09

01 Jan '09

Dear GPC, The African Chief maintains the Windows version of GPC, now using 20070904 sources. Adriaan maintains the MacOS version, now using 20070904 sources. I think the outstanding question for Prince and me is the Linux version. There is no binary distribution of the 20070904 GPC that I can find. I use the 20041218 version on Linux. I suppose most Linux users are happy to compile GPC from sources. But I'm not a Linux expert: I just port my code to Linux for my Linux users. So I'm … [View More]

8 21

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