[fpc-devel] Bootstrap fixes_2_4 x86_64 using 2.2.4 i386 error : __missing_command_CMP
Hi all, when i tried to bootstrap a x86_64 compiler from fixes_2_4 branch using a stable i386 ppc386 2.2.4 i got this error: fixes_2_4 branch revision : 13817 ppc386 -i : Free Pascal Compiler version 2.2.4, Compiler Date : 2009/04/10, Compiler CPU Target: i386 make all install UPXPROG=echo INSTALL_PREFIX=C:\Users\dimitris\Documents\Programming\FreePascal\fp c FPC=C:\Users\dimitris\Documents\Programming\FreePascal\FpcRel\ppc386.exe " ... process_begin: CreateProcess((null), __missing_command_CMP -i218 C:/Users/dimitr is/Documents/Programming/FreePascal/fpc/source/compiler/ppc2.exe C:/Users/dimitr is/Documents/Programming/FreePascal/fpc/source/compiler/ppc3.exe, ...) failed. make[3]: Entering directory `C:/Users/dimitris/Documents/Programming/FreePascal/ fpc/source/compiler' C:/Users/dimitris/Documents/Programming/FreePascal/fpc/source/compiler/ppc2.exe and C:/Users/dimitris/Documents/Programming/FreePascal/fpc/source/compiler/ppc3. exe are equal C:/Users/dimitris/Documents/Programming/FreePascal/binutils/x86_64-win64/cp.exe -fp C:/Users/dimitris/Documents/Programming/FreePascal/fpc/source/compiler/ppc3. exe ppc386.exe make[3]: Leaving directory `C:/Users/dimitris/Documents/Programming/FreePascal/f pc/source/compiler' __missing_command_CMP -i218 ppc3.exe ppc386.exe process_begin: CreateProcess((null), __missing_command_CMP -i218 ppc3.exe ppc386 .exe, ...) failed. make (e=2): The system cannot find the file specified. make[2]: *** [cycle] Error 2 make[2]: Leaving directory `C:/Users/dimitris/Documents/Programming/FreePascal/f pc/source/compiler' make[1]: *** [compiler_cycle] Error 2 make[1]: Leaving directory `C:/Users/dimitris/Documents/Programming/FreePascal/f pc/source' make: *** [build-stamp.i386-win32] Error 2 ..." Any hint ? Is it a bug ? regards, -- Dimitrios Chr. Ioannidis ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] make all OPT="gtl"
On 07 Oct 2009, at 22:24, Vincent Snijders wrote: Should I create a bug report or is using -gt for the compiler not supported. It should work. There is one problem with compiling the RTL with -gt if you assign a shortstring to itself (e.g., by passing a global variable variable as var/const-parameter to a function, which then assigns this var parameter to that global variable) on targets that don't use an assembler helper for this. And the compiler does this somewhere while parsing the command line options. However, I assume this is on i386 and that one does use an assembler helper. Furthermore, that problem only causes the compiler not to compile anything, rather than crash during parsing. Jonas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Bootstrap fixes_2_4 x86_64 using 2.2.4 i386 error : __missing_command_CMP
On 08 Oct 2009, at 09:32, Dimitrios Chr. Ioannidis wrote: when i tried to bootstrap a x86_64 compiler from fixes_2_4 branch using a stable i386 ppc386 2.2.4 i got this error: I would recommend to not cross-bootstrap across different versions. Jonas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] SetString difference between Ansistring and UnicodeString
Vincent Snijders schreef: Vincent Snijders schreef: While running valgrind on fpcdoc, I got a warning in Maybe you are interested in the valgind output. See attachment. Another problem, that was also in the valgrind output (reading uninitialized memory): EAccessViolation : Access violation $08099882 TNODEPOOL__DESTROY, line 3304 of src/dom.pp $080BFF73 THTMLWRITER__WRITEDOC, line 3341 of dw_html.pp $08049809 CREATEDOCUMENTATION, line 267 of fpdoc.pp $08049A00 main, line 290 of fpdoc.pp Vincent ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] SetString difference between Ansistring and UnicodeString
In our previous episode, Vincent Snijders said: > > Vincent Snijders schreef: > >> While running valgrind on fpcdoc, I got a warning in > > > > Maybe you are interested in the valgind output. See attachment. > > > > Another problem, that was also in the valgrind output (reading uninitialized > memory): > EAccessViolation : Access violation >$08099882 TNODEPOOL__DESTROY, line 3304 of src/dom.pp >$080BFF73 THTMLWRITER__WRITEDOC, line 3341 of dw_html.pp >$08049809 CREATEDOCUMENTATION, line 267 of fpdoc.pp >$08049A00 main, line 290 of fpdoc.pp Nodepool and friends use objects on non-allocated memory. It might be that valgrind doesn't understand that. I think DOM should have a define to turn that off, for debugging purposes. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] SetString difference between Ansistring and UnicodeString
Marco van de Voort schreef: In our previous episode, Vincent Snijders said: Vincent Snijders schreef: While running valgrind on fpcdoc, I got a warning in Maybe you are interested in the valgind output. See attachment. Another problem, that was also in the valgrind output (reading uninitialized memory): EAccessViolation : Access violation $08099882 TNODEPOOL__DESTROY, line 3304 of src/dom.pp $080BFF73 THTMLWRITER__WRITEDOC, line 3341 of dw_html.pp $08049809 CREATEDOCUMENTATION, line 267 of fpdoc.pp $08049A00 main, line 290 of fpdoc.pp Nodepool and friends use objects on non-allocated memory. It might be that valgrind doesn't understand that. I think DOM should have a define to turn that off, for debugging purposes. Well, this AV is from a build with gt, which seems to suggest that the nodepool is reading from uninitialized memory. I doubt that the valgrind warning is false. I admit these are mere hints at a possible bug, but if I were maintainer of that code, I would take another look at it. Vincent ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] SetString difference between Ansistring and UnicodeString
Vincent Snijders wrote: I admit these are mere hints at a possible bug, but if I were maintainer of that code, I would take another look at it. I will :-) Sergei ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Bug in FPC 2.2.2 asm, Win64 target
When compiling the following code for Win64 using FPC 2.2.2, Intel syntax mov qword [rdx ],$08C9BCF367E6096A the compiler generates a movl instruction for just the least significant half of the constant qword movl 0x67e6096a,(%rdx) Am I missing something obvious? smime.p7s Description: S/MIME Cryptographic Signature ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Bug in FPC 2.2.2 asm, Win64 target
On 08 Oct 2009, at 14:54, Henrick Hellström wrote: When compiling the following code for Win64 using FPC 2.2.2, Intel syntax mov qword [rdx ],$08C9BCF367E6096A the compiler generates a movl instruction for just the least significant half of the constant qword movl 0x67e6096a,(%rdx) Am I missing something obvious? Very recently someone reported a bug about this: http://bugs.freepascal.org/view.php?id=14685 Jonas___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] gdb 7.0 new features
Hello, FPC developers' list What of new gdb 7.0 features will be used by FPC? I see only 3 features: - Multi-byte and wide character set support GDB has a new data type or what? Will fpc use that datatype? - Inlined functions are now supported Currently I can't enter an inlined function using step into. Breakpoints don't work in the inlined functions too. As I understand now it will be possible to implement in fpc? - GDB is now able to read compressed debug sections What does this give? Smaller debug info? If so then will fpc support this? Maybe I missed some other gdb 7.0 new feature which is useful for fpc/lazarus? Best regards, Paul Ishenin. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] gdb 7.0 new features
On 08 Oct 2009, at 16:28, Paul Ishenin wrote: I see only 3 features: - Multi-byte and wide character set support GDB has a new data type or what? Will fpc use that datatype? It does not require any changes in FPC. Afaik it means that if you have a widechar (or an array of widechar, or a pwidechar), GDB should now interpret that data as utf-16 when printing it. - Inlined functions are now supported Currently I can't enter an inlined function using step into. Breakpoints don't work in the inlined functions too. As I understand now it will be possible to implement in fpc? Yes - GDB is now able to read compressed debug sections What does this give? Smaller debug info? Probably. If so then will fpc support this? When someone implements it. I assume that that if you use an external assembler/linker, you can already use it today. Maybe I missed some other gdb 7.0 new feature which is useful for fpc/lazarus? Reverse debugging sounds pretty useful to me (only supported under Linux/i386 and Linux/x86_64 for now though, and has some limitations). The Python scripting support could also be useful to create a standard "library" of routines to print Pascal types in a nice way for which native support in gdb is not yet present. Jonas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] New global CustomApplication variable
Hi all, In fpc 2.5.1 I've introduced the global CustomApplication variable in the custapp unit. The idea is that when this variable is set when a application-object is initialized, this variable is set so that you can access the CustomApplication-object without knowing in which unit it is defined. We've discussed this before. I want to know if the current implementation is usefull for the existing application-frameworks like Lazarus and MSEIde. If that's so I'll maybe merge it to fpc 2.3.1. Joost. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] SetString difference between Ansistring and UnicodeString
Sergei Gorelkin wrote: Vincent Snijders wrote: I admit these are mere hints at a possible bug, but if I were maintainer of that code, I would take another look at it. I will :-) Vincent, what command(s) did you use to get that log? What options were used when compiling the packages? Sergei ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] gdb shows wrong type info
Hello, FPC developers' list. This was reported few days ago on the Lazarus mail list and probably was not noticed by FPC developers: Compile any application with stabs debug info (I did not check with dwarf), run it in gdb: (gdb) ptype Exception type = EXCEPTION = class : public TOBJECT private FMESSAGE : ANSISTRING; FHELPCONTEXT : LONGINT; public constructor CREATE (EXCEPTION, POINTER, ANSISTRING) : ^EXCEPTION; constructor CREATEFMT (EXCEPTION, POINTER, ANSISTRING, unnamedtype, ONGINT) : ^EXCEPTION; constructor CREATERES (EXCEPTION, POINTER, PSTRING) : ^EXCEPTION; constructor CREATERESFMT (EXCEPTION, POINTER, PSTRING, unnamedtype, ONGINT, ) : ^EXCEPTION; constructor CREATEHELP (EXCEPTION, POINTER, ANSISTRING, ONGINT) : ^EXCEPTION; constructor CREATEFMTHELP (EXCEPTION, POINTER, ANSISTRING, unnamedtype, ONGINT7, ) : ^EXCEPTION; constructor CREATERESHELP (EXCEPTION, POINTER, PSTRING, LONGINT) : ^EXCEPTION; constructor CREATERESFMTHELP (EXCEPTION, POINTER, PSTRING, unnamedtype, ONGINT7, ) : ^EXCEPTION; end If you look carefully at the gdb output you can notice the next types: 1. ONGINT 2. ONGINT7 Same if you check gdb output for TObject (and even more - "OINTER" type is there). Is this known? Is this a bug? -- Best regards, Paul Ishenin. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
