Gpc November 2001

gpc@gnu.de

28 participants
70 discussions

GPC.p/test/test_sum script problem
by Mirsad Todorovac 09 Nov '01

09 Nov '01

Hi, -------------------------------------------------------------------------- 1. grep -e: -------------------------------------------------------------------------- p/test/test_run uses grep -e option that is not allowed in Solaris' default grep (I guess somebody in Sun likes archaeology): > /usr/bin/grep -e w /usr/bin/grep: illegal option -- e Usage: grep -hblcnsviw pattern file . . . /usr/xpg4/bin/grep understands this option without problems, so after I've added a symlink to /usr/xpg4/bin/grep in ~/bin testsuite ran OK. -------------------------------------------------------------------------- 2. gawk, awk, nawk: -------------------------------------------------------------------------- ``awk'' and ``nawk'' don't seem to understand ``fflush'' function used in p/test/test_sum script - they break at it. If GNU gawk is not installed, editing of the script is required. -------------------------------------------------------------------------- 3. alpha-sof-4.0b/gawk: -------------------------------------------------------------------------- On Alpha/OSF1/DU4.0b systems there is an ancient example of gawk installed in /usr/bin which neither understands long options, neither fflush() function (if it's GNU at all?), so the script breaks - I bailed out again with symlinking /usr/local/bin/gawk to ~/bin, but I feel it's kind of clumsy. Yes, and if you consider me worthy I'd be happy to help :-) Best regards, Mirsad -- This message has been made up using recycled ideas and language constructs. No plant or animal has been injured in process of making this message.

2 2

Support for PowerMax OS
by Sven Jauring 09 Nov '01

09 Nov '01

Hi all Is it possible to use GPC for (Concurrent's) PowerMax operating system? I looked through the GPC distribution (20010924), but didn't find anything about PowerMax. Best Regards Sven Jauring

1 0

Re: ANNOUNCE: gcc-3.0.2 for DJGPP
by da Silva, Joe 09 Nov '01

09 Nov '01

This matter has been raised before, so I'm just repeating what was said previously (I don't know about the issues involved;-) : GPC is currently compatible with GCC 2.95.3 but not GCC 3.X.X, although it is intended that some time in the future, it will be made compatible with whatever is the current version of GCC ... Joe. PS - BTW, is your "worldnet.att.net" e-mail address still used? > -----Original Message----- > From: CBFalconer [SMTP:cbfalconer@yahoo.com] > Sent: Friday, November 09, 2001 8:06 AM > To: gpc mail-list > Subject: Re: ANNOUNCE: gcc-3.0.2 for DJGPP > > pavenis(a)lanet.lv wrote: > > > > This is an announcement of DJGPP port of gcc-3.0.2 > > > > GCC used to stand for the GNU C Compiler, but since the compiler > > supports several other languages aside from C, it now stands for > > the GNU Compiler Collection. > > > > GCC 3.0.x has several new optimizations, new targets, new languages > > and many other new features, relative to GCC 2.95.x. See the new > > features page for a more complete list. > > > > See http://gcc.gnu.org/gcc-3.0/ for more information about gcc-3.0.2 > > > > Currently C, C++, Fortran and Objective C compilers are supported > > for DJGPP. Java compiler is not ported and is not included > > > > Also libg++ is no more included and will not be included in future. > > > > Archives are available from DJGPP distribution in Simtelnet > > (and mirror sites) in directory v2gnu: > > http://www.simtel.net/pub/djgpp/v2gnu/ > > > > There are 6 archives: > > readme-gcc-3.0.2.txt - readme file from DJGPP port of GCC-3.0.2. It's > in > > separate file to avoid need to download large archives > > to get this file. > > gcc302s.zip - sources of gcc-3.0.2. I put all sources in a single > > archive. This file is only needed if You're want to > > rebuild gcc-3.0.2 from sources. > > gcc302b.zip - binaries of C compiler > > gpp302b.zip - binaries of C++ compiler (needs gcc302b.zip) > > g77302b.zip - binaries of Fortran compiler (needs gcc302b.zip) > > objc302b.zip - binaries of Objective C compiler (needs gcc302b.zip) > > gcc302s2.zip - shell script and patches for original gcc-3.0.2. > > I used them to generate gcc-3.0.2 sources for DJGPP > > (gcc2953s.zip). > > > > Files user need: > > Programming languages Needed files > > C gcc302b.zip > > C++ gcc302b.zip, gpp302b.zip > > Fortran gcc302b.zip, g77302b.zip > > Objective-C gcc302b.zip, objc302b.zip > > > > NOTE: gcc302b.zip contains file cxxfilt.exe and there is file with same > name in > > binutils (bnu2112b.zip). You can safely overwrite the old one. > > > > For more information about this port see archive > > gnu/gcc-3.02/readme.DJGPP > > after unpacking either gcc302b.zip or gcc302s.zip or get file > > readme-gcc-3.0.2.txt from directory v2gnu in DJGPP distribution > > > > Also please DON'T mix C++ libraries (or object files) built with > > different compiler versions. C++ sources should be recompiled (seems > > that there is no need to do this for C sources). > > > > System requirements > > =================== > > > > DJGPP-2.03 or above (otherwise exceptions will not work at all) > > > > binutils-2.11.2 or above. It's no more possible to use binutils-2.8.1 > > or 2.9.1. Command line option -mno-bnu210 is no more supported. > > > > Some warning for users of C++. C++ compiler in gcc-3.0.2 does more > strict > > syntax checking than gcc and egcs versions older than gcc-3.0. As result > > errors are generated in many places where earlier one got warnings. > > What about the gpc package? It presently wants the gcc 2.9.5.3 > package? > > -- > Chuck F (cbfalconer(a)yahoo.com) (cbfalconer(a)XXXXworldnet.att.net) > Available for consulting/temporary embedded and systems. > (Remove "XXXX" from reply address. yahoo works unmodified) > mailto:uce@ftc.gov (for spambots to harvest) > >

2 1

Re: ANNOUNCE: gcc-3.0.2 for DJGPP
by CBFalconer 08 Nov '01

08 Nov '01

pavenis(a)lanet.lv wrote: > > This is an announcement of DJGPP port of gcc-3.0.2 > > GCC used to stand for the GNU C Compiler, but since the compiler > supports several other languages aside from C, it now stands for > the GNU Compiler Collection. > > GCC 3.0.x has several new optimizations, new targets, new languages > and many other new features, relative to GCC 2.95.x. See the new > features page for a more complete list. > > See http://gcc.gnu.org/gcc-3.0/ for more information about gcc-3.0.2 > > Currently C, C++, Fortran and Objective C compilers are supported > for DJGPP. Java compiler is not ported and is not included > > Also libg++ is no more included and will not be included in future. > > Archives are available from DJGPP distribution in Simtelnet > (and mirror sites) in directory v2gnu: > http://www.simtel.net/pub/djgpp/v2gnu/ > > There are 6 archives: > readme-gcc-3.0.2.txt - readme file from DJGPP port of GCC-3.0.2. It's in > separate file to avoid need to download large archives > to get this file. > gcc302s.zip - sources of gcc-3.0.2. I put all sources in a single > archive. This file is only needed if You're want to > rebuild gcc-3.0.2 from sources. > gcc302b.zip - binaries of C compiler > gpp302b.zip - binaries of C++ compiler (needs gcc302b.zip) > g77302b.zip - binaries of Fortran compiler (needs gcc302b.zip) > objc302b.zip - binaries of Objective C compiler (needs gcc302b.zip) > gcc302s2.zip - shell script and patches for original gcc-3.0.2. > I used them to generate gcc-3.0.2 sources for DJGPP > (gcc2953s.zip). > > Files user need: > Programming languages Needed files > C gcc302b.zip > C++ gcc302b.zip, gpp302b.zip > Fortran gcc302b.zip, g77302b.zip > Objective-C gcc302b.zip, objc302b.zip > > NOTE: gcc302b.zip contains file cxxfilt.exe and there is file with same name in > binutils (bnu2112b.zip). You can safely overwrite the old one. > > For more information about this port see archive > gnu/gcc-3.02/readme.DJGPP > after unpacking either gcc302b.zip or gcc302s.zip or get file > readme-gcc-3.0.2.txt from directory v2gnu in DJGPP distribution > > Also please DON'T mix C++ libraries (or object files) built with > different compiler versions. C++ sources should be recompiled (seems > that there is no need to do this for C sources). > > System requirements > =================== > > DJGPP-2.03 or above (otherwise exceptions will not work at all) > > binutils-2.11.2 or above. It's no more possible to use binutils-2.8.1 > or 2.9.1. Command line option -mno-bnu210 is no more supported. > > Some warning for users of C++. C++ compiler in gcc-3.0.2 does more strict > syntax checking than gcc and egcs versions older than gcc-3.0. As result > errors are generated in many places where earlier one got warnings. What about the gpc package? It presently wants the gcc 2.9.5.3 package? -- Chuck F (cbfalconer(a)yahoo.com) (cbfalconer(a)XXXXworldnet.att.net) Available for consulting/temporary embedded and systems. (Remove "XXXX" from reply address. yahoo works unmodified) mailto:uce@ftc.gov (for spambots to harvest)

1 0

Subrange Bug with indentation?
by Eike Lange 08 Nov '01

08 Nov '01

Hi Folks! The following program compiles correctly (shouldn't there a warning?). &<---------- (snip) ----------- program fail; type TFoo = 2.7 .. 2.8; var MyFoo: TFoo; begin MyFoo := 1.0; WriteLn (MyFoo) end. &<---------- (snap) ----------- Notice, that you need spaces arround ".." to disable warning messages: "fail.pas:4: Only one decimal point in real number allowed" My GPC version is: Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/specs gpc version 20010924, based on 2.95.2 19991024 (release) Eike

3 3

Re: win32 GPC blues
by Pierre Muller 06 Nov '01

06 Nov '01

At 15:02 06/11/2001 , Prof. A Olowofoyeku (The African Chief) a écrit: >On 6 Nov 2001, at 13:39, Pierre Muller wrote: > > > Trying to get strings output for GPC to work, > > I needed a win32 gpc binary to check my changes to GDB. > > > > But I have problems both with the latest cygwin binary port > > ftp://agnes.dida.physik.uni-essen.de/home/chief/win32/cygwin/2.95.3/gpc-20 > > 01 0924.i686-pc-cygwin.tar.gz > >That version (0924) is broken under Windows. I haven't had time to >investigate why, because I simply regressed to 0623 at the time. I >thought I had removed 0924 from agnes, but perhaps forgot to do so (I >have done so now). Please get the 0623 version instead. I downloaded that version but I still have the same problem.... $ gpc -v Reading specs from /usr/local/lib/gcc-lib/i686-pc-cygwin/2.95.3/specs gpc version 20010623, based on 2.95.3 20010315 (release) >[...] > > as > > Assembler messages: > > for reading open > > : No such file or directory > >This is most likely a mount problem. For some reason, it seems that you >need to mount your volumes in textmode instead of binary. I don't understand, what change should I make to my mount.... I only had binary mounts but I tried to a a textmode mount to a directory that contains some pascal source code. But this does not change anything :( I still get the same error from as, both for a file on a binmode mount and on a textmode mount. > > Remebering that mingw32 is the prefered win32 version, I tried to download > > the latest gpc for mingw32, but here again, I had problems. >[...] > > -lmsvcr t -luser32 -lkernel32 -ladvapi32 -lshell32 -lmingw32 -lgcc > > -lmoldname -lmsvcrt gpc: installation problem, cannot exec `collect2': No > > such file or directory > > > > > > I have the correct gcc installed, but gpc needs collect2, where should I > > find that binary ? > >Simply copy 'ld.exe' to 'collect2.exe'. I also tried this, but here again, I only made a small step forward: I does go up to linking but then I get this : F:\pas\cvs100\ide>gpc -v hello.pp -Lf:\mingw32\lib Reading specs from f:\mingw32\usr\local\lib\gcc-lib\i386-mingw32msvc\2.95.3\spec s gpc version 20010331, based on 2.95.2 19991024 (release) f:\mingw32\usr\local\lib\gcc-lib\i386-mingw32msvc\2.95.3\gpcpp.exe -lang-pascal -v -iprefix f:/mingw32/usr/local/lib/gcc-lib/i386-mingw32msvc/2.95.3/i386-mingw 32msvc\2.95.2\ -famtmpfile=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca02196 -fdelphi- comments -D__GNU_PASCAL__ -undef -D__GNUC__=2 -D__GNUC_MINOR__=95 -D__GPC__=2 -D __GPC_MINOR__=0 -D__GPC_RELEASE__=20010331 -D__BITS_LITTLE_ENDIAN__=1 -D__BYTES_ LITTLE_ENDIAN__=1 -D__WORDS_LITTLE_ENDIAN__=1 -Di386 -D_WIN32 -DWIN32 -D__WIN32_ _ -D__MINGW32__=0.2 -D__MSVCRT__ -DWINNT -D_X86_=1 -D__STDC__=1 -D__stdcall=__at tribute__((__stdcall__)) -D_stdcall=__attribute__((__stdcall__)) -D__cdecl=__att ribute__((__cdecl__)) -D__declspec(x)=__attribute__((x)) -D__OS_DOS__=1 -D__i386 __ -D_WIN32 -D__WIN32__ -D__WIN32__ -D__MINGW32__=0.2 -D__MSVCRT__ -D__WINNT__ - D_X86_=1 -D__STDC__=1 -D__stdcall=__attribute__((__stdcall__)) -D___stdcall__=__ attribute__((__stdcall__)) -D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)= __attribute__((x)) -D__OS_DOS__=1 -D__i386 -D__WIN32 -D__WINNT -D___stdcall=__at tribute__((__stdcall__)) -Asystem(winnt) -Acpu(i386) -Amachine(i386) -remap -Acp u(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ hello.pp C:\DOCUME~1\ADMINI~1 \LOCALS~1\Temp\cca02196.i GNU Pascal Compiler PreProcessor version 20010623, based on gcc-2.95.3 20010315 (release) (80386, BSD syntax) #include "..." search starts here: #include <...> search starts here: f:/mingw32/usr/local/lib/gcc-lib/i386-mingw32msvc/2.95.3/i386-mingw32msvc\ f:/mingw32/usr/local/lib/gcc-lib/i386-mingw32msvc/2.95.3/i386-mingw32msvc\2.95. 2\include /usr/local/include /include /usr/local/lib/gcc-lib/i386-mingw32msvc/2.95.3/include /usr/local/i386-mingw32/include End of search list. f:\mingw32\usr\local\lib\gcc-lib\i386-mingw32msvc\2.95.3\gpc1.exe C:\DOCUME~1\A DMINI~1\LOCALS~1\Temp\cca02196.i -quiet -dumpbase hello.pas -version -famtmpfile =C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca02196 -o C:\DOCUME~1\ADMINI~1\LOCALS~1\Te mp\cca02196.s GNU Pascal version 2.95.3 20010315 (release) (i386-mingw32msvc) compiled by GNU C version 3.0. GNU Pascal version is actually 20010623, based on gcc-2.95.3 20010315 (release) hello.pp:1: warning: missing program header as -o C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca021961.o C:\DOCUME~1\ADMINI~1\LOCAL S~1\Temp\cca02196.s collect2 crt2.o -Lf:\mingw32\lib -Lf:\mingw32\usr\local\lib\gcc-lib\i386-mingw3 2msvc\2.95.3 -Lf:\mingw32\usr\local\lib\gcc-lib\i386-mingw32msvc\2.95.3\i386-min gw32msvc\2.95.2\..\..\.. C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\cca021961.o -lgpc -l mingw32 -lgcc -lmoldname -lmsvcrt -luser32 -lkernel32 -ladvapi32 -lshell32 -lmin gw32 -lgcc -lmoldname -lmsvcrt collect2: cannot open crt2.o: No such file or directory Note that I added -Lf:\mingw32\lib to the command line options and this is the location of this crt2.o file ... Using / instead of \ or changing the option position on command line doesn't change the result. Anyway, I don't think its used for single files ... Pierre Muller Institut Charles Sadron 6,rue Boussingault F 67083 STRASBOURG CEDEX (France) mailto:muller@ics.u-strasbg.fr Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99

3 3

[RFA] Unify pascal string printing
by Pierre Muller 06 Nov '01

06 Nov '01

This change will allow to display GPC stings nicely as Free Pascal strings are already. The method is pretty generic and adding new types (widestings or ansistrings) should be easy. ChangeLog: 2001-11-06 Pierre Muller <muller(a)ics.u-strasbg.fr> * p-lang.c (is_pascal_string_type): new function to determine if a type is a string type. * p-valprint.c (pascal_val_print) : use is_pascal_string_type function to display strings nicely. Index: p-lang.c =================================================================== RCS file: /cvs/src/src/gdb/p-lang.c,v retrieving revision 1.3 diff -u -r1.3 p-lang.c --- p-lang.c 2000/08/11 01:02:35 1.3 +++ p-lang.c 2001/11/06 16:02:53 @@ -17,7 +17,7 @@ along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ -/* This file is derived from p-lang.c */ +/* This file is derived from c-lang.c */ #include "defs.h" #include "symtab.h" @@ -27,8 +27,56 @@ #include "language.h" #include "p-lang.h" #include "valprint.h" - +#include <ctype.h> + extern void _initialize_pascal_language (void); + + +/* Determines if type TYPE is a pascal string type. + Returns 1 if the type is a known pascal 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 + length_pos, length_size and string_pos are given in bytes. + char_size gives the element size in bytes. + FIXME: if the position or the size of these fields + are not multiple of TARGET_CHAR_BIT then the results are wrong + but this does not happen for Free Pascal nor for GPC */ +int +is_pascal_string_type (struct type *type,int *length_pos, + int * length_size, int *string_pos, int *char_size) +{ + if (TYPE_CODE (type) == TYPE_CODE_STRUCT) + { + /* Old Borland type pascal strings from Free Pascal Compiler */ + /* Two fields: length and st */ + if (TYPE_NFIELDS (type) == 2 && + strcmp (TYPE_FIELDS (type)[0].name, "length") == 0 && + strcmp (TYPE_FIELDS (type)[1].name, "st") == 0) + { + *length_pos = TYPE_FIELD_BITPOS (type, 0) / TARGET_CHAR_BIT; + *length_size = TYPE_FIELD_TYPE (type, 0)->length; + *string_pos = TYPE_FIELD_BITPOS (type, 1) / TARGET_CHAR_BIT; + *char_size = 1; + return 1; + }; + /* GNU pascal strings */ + /* Three fields: Capacity, length and schema$ or _p_schema */ + if (TYPE_NFIELDS (type) == 3 && + strcmp (TYPE_FIELDS (type)[0].name, "Capacity") == 0 && + strcmp (TYPE_FIELDS (type)[1].name, "length") == 0) + { + *length_pos = TYPE_FIELD_BITPOS (type, 1) / TARGET_CHAR_BIT; + *length_size = TYPE_FIELD_TYPE (type, 1)->length; + *string_pos = TYPE_FIELD_BITPOS (type, 2) / TARGET_CHAR_BIT; + /* FIXME: how can I detect wide chars in GPC ?? */ + *char_size = 1; + return 1; + }; + } + return 0; +} + static void pascal_one_char (int, struct ui_file *, int *); /* Print the character C on STREAM as part of the contents of a literal Index: p-valprint.c =================================================================== RCS file: /cvs/src/src/gdb/p-valprint.c,v retrieving revision 1.4 diff -u -r1.4 p-valprint.c --- p-valprint.c 2001/03/27 20:36:24 1.4 +++ p-valprint.c 2001/11/06 16:02:53 @@ -40,6 +40,7 @@ + /* Print data of type TYPE located at VALADDR (within GDB), which came from the inferior at address ADDRESS, onto stdio stream STREAM according to FORMAT (a letter or 0 for natural format). The data at VALADDR is in @@ -53,7 +54,6 @@ The PRETTY parameter controls prettyprinting. */ - int pascal_val_print (struct type *type, char *valaddr, int embedded_offset, CORE_ADDR address, struct ui_file *stream, int format, @@ -63,6 +63,8 @@ unsigned len; struct type *elttype; unsigned eltlen; + int length_pos, length_size, string_pos; + int char_size; LONGEST val; CORE_ADDR addr; @@ -188,15 +190,17 @@ Pascal strings are mapped to records with lowercase names PM */ /* I don't know what GPC does :( PM */ - if (TYPE_CODE (elttype) == TYPE_CODE_STRUCT && - TYPE_NFIELDS (elttype) == 2 && - strcmp (TYPE_FIELDS (elttype)[0].name, "length") == 0 && - strcmp (TYPE_FIELDS (elttype)[1].name, "st") == 0 && - addr != 0) + if ( is_pascal_string_type (elttype, &length_pos, + &length_size, &string_pos, &char_size) && + addr != 0) { - char bytelength; - read_memory (addr, &bytelength, 1); - i = val_print_string (addr + 1, bytelength, 1, stream); + ULONGEST string_length; + void *buffer; + buffer = xmalloc(length_size); + read_memory(addr + length_pos, buffer, length_size); + string_length = extract_unsigned_integer (buffer, length_size); + xfree(buffer); + i = val_print_string (addr + string_pos, string_length, char_size , stream); } else if (pascal_object_is_vtbl_member (type)) { @@ -315,12 +319,11 @@ } else { - if ((TYPE_NFIELDS (type) == 2) && - (strcmp (TYPE_FIELDS (type)[0].name, "length") == 0) && - (strcmp (TYPE_FIELDS (type)[1].name, "st") == 0)) + if ( is_pascal_string_type (type, &length_pos, &length_size, + &string_pos, &char_size)) { - len = (*(valaddr + embedded_offset)) & 0xff; - LA_PRINT_STRING (stream, valaddr + embedded_offset + 1, len, /* width ?? */ 0, 0); + len = extract_unsigned_integer(valaddr + embedded_offset + length_pos, length_size); + LA_PRINT_STRING (stream, valaddr + embedded_offset + string_pos, len, char_size, 0); } else pascal_object_print_value_fields (type, valaddr + embedded_offset, address, stream, format, Pierre Muller Institut Charles Sadron 6,rue Boussingault F 67083 STRASBOURG CEDEX (France) mailto:muller@ics.u-strasbg.fr Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99

1 0

[RFA] p-exp.y uppercasing change
by Pierre Muller 06 Nov '01

06 Nov '01

In order to allow GPC compiled programs to find fields of structures, I need to change p-exp.y so that the case is only modifed if the symbol is really found. I also added a check for the standard GPC case which uses names in capitalized form (i.e. first char in uppercase, rest in lowercase). Note: before this patch, it is impossible to get any field of a record (pascal structure) compiled with GPC. Should I consider changing 5.1 branch also ? Changelog: 2001-11-06 Pierre Muller <muller(a)ics.u-strasbg.fr> * p-exp.y (): only change case of expression if symbol is found. Also check for GPC standard name form. Index: p-exp.y =================================================================== RCS file: /cvs/src/src/gdb/p-exp.y,v retrieving revision 1.6 diff -u -r1.6 p-exp.y --- p-exp.y 2001/06/10 16:25:51 1.6 +++ p-exp.y 2001/11/06 15:27:02 @@ -1306,14 +1306,48 @@ { if ((tmp[i]>='a' && tmp[i]<='z')) tmp[i] -= ('a'-'A'); - /* I am not sure that copy_name gives excatly the same result ! */ + } + sym = lookup_symbol (tmp, expression_context_block, + VAR_NAMESPACE, + &is_a_field_of_this, + (struct symtab **) NULL); + if (sym) + for (i = 0;i <= namelen;i++) + { if ((tokstart[i]>='a' && tokstart[i]<='z')) tokstart[i] -= ('a'-'A'); + } + } + /* Third chance Capitalized (as GPC does) */ + if (!sym) + { + for (i = 0;i <= namelen;i++) + { + if (i==0) + { + if ((tmp[i]>='a' && tmp[i]<='z')) + tmp[i] -= ('a'-'A'); + } + else + if ((tmp[i]>='A' && tmp[i]<='Z')) + tmp[i] -= ('A'-'a'); } - sym = lookup_symbol (tmp, expression_context_block, + sym = lookup_symbol (tmp, expression_context_block, VAR_NAMESPACE, &is_a_field_of_this, (struct symtab **) NULL); + if (sym) + for (i = 0;i <= namelen;i++) + { + if (i==0) + { + if ((tokstart[i]>='a' && tokstart[i]<='z')) + tokstart[i] -= ('a'-'A'); + } + else + if ((tokstart[i]>='A' && tokstart[i]<='Z')) + tokstart[i] -= ('A'-'a'); + } } /* Call lookup_symtab, not lookup_partial_symtab, in case there are no psymtabs (coff, xcoff, or some future change to blow away the Pierre Muller Institut Charles Sadron 6,rue Boussingault F 67083 STRASBOURG CEDEX (France) mailto:muller@ics.u-strasbg.fr Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99

1 0

Re: Re :Typecasting | record-field boundary
by Frank Heckenbach 05 Nov '01

05 Nov '01

Anuradha wrote: > The machine i am working with is sparc sun-solaris.Can you tell me more > on the alignment problem? Yes, Sparcs have strict alignment requirements. So I suggest to either use `SizeOf (LongestInt)' instead of 2 or, as I already said, avoid the extra code entirely and just use GetMem/FreeMem (the latter with only one argument if you like) instead of getmemory/freememory (provided you don't need the extra size information for any other purpose besides freememory). > I don't get the error with the original code if i just add "packed" > before the "record". GPC generates special code for packed records which avoids the alignment problem, but it clearly less efficient. Frank -- Frank Heckenbach, frank(a)g-n-u.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Re: Re :Typecasting | record-field boundary
by da Silva, Joe 05 Nov '01

05 Nov '01

Hey - you're right! "Word" is (usually) 32 bits for GPC. Lesson : Read the latest doc's, don't rely on the old ones! <G> Anyway, this issue shouldn't matter for the sample code presented, so we'll wait for some more input from Anuradha ... Joe. > -----Original Message----- > From: Frank Heckenbach [SMTP:frank@g-n-u.de] > Sent: Monday, November 05, 2001 12:00 PM > To: gpc(a)gnu.de > Subject: Re: Re :Typecasting | record-field boundary > > da Silva, Joe wrote: > > > Since the code "works with BP but not GPC", I presumed the > > hardware was X86 (IA32) ... I think Anuradha needs to clarify > > this, because as you say, misaligned access may not work > > with some other processors. BTW, the code also requires that > > a "word" is 16 bits - since the documentation implies that this > > is not true on all hardware, > > In fact, for GPC this is true for *none* of the platforms -- > `Integer' and `Word' are at least 32 bit (64 on some). Of course, > you can redeclare `Word' (see the System unit), though this is not > recommended. > > > this is another potential problem > > with the code. > > I think I mentioned this in my last mail. > > Frank > > -- > Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ > GPC To-Do list, latest features, fixed bugs: > http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

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 November 2001