Re: [fpc-devel] Missing command line parameters in Linux FPC
Jonas Maebe het geskryf: > > It's unrelated to Linux vs Windows. Those options are enabled/disabled > per architecture, and I bet you are using a 32 bit Windows and a 64 > bit Linux FPC binary. Exactly what I was using. :-) > It's quite possible that some that are not shown > for x86-64 while they should be though. Those parameters are very handy if you are in a rush to create some build script (for various platforms, even though I am currently in 64-bit Linux). A quick 'fpc -h' to find the information without having to hunt through the various FPC PDF docs. That's why I think it will be very handy if parameter information is displayed on all platforms. Just a thought (or maybe it's because I'm lazy searching the PDF's). ;-) Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/ ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] dward debug info - someone promiced more compact debug info than stabs
On Tue, Mar 16, 2010 at 12:41 PM, Paul Ishenin wrote: > 16.03.2010 22:33, Jonas Maebe wrote: >>> Why dwarf information has so big debug files (comparing with stabs) on windows? >>> >>> Because Windows (just like Darwin) does not support referring to DWARF >>> debug info from one object file to another, so a lot of debug information is >>> duplicated in multiple units. >> >> We also encode more information when using DWARF than when using Stabs >> (e.g. properties, absolute variables, public/private/protected information, >> calling convention, virtuality of methods). > > But 200 Mb of info for 10Mb executable is too much. How do you think? I > don't believe that other compilers on windows generates so fat output for > dwarf. Do you know any similar numbers for gcc? > > Best regards, > Paul Ishenin. Haven't you ever used MSVC++? ;) -Flávio ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Missing command line parameters in Linux FPC
On Tue, 16 Mar 2010, Jonas Maebe wrote: On 16 Mar 2010, at 08:44, Graeme Geldenhuys wrote: Under Linux the following information is missing, yet this information is displayed in the Windows version of FPC. It's unrelated to Linux vs Windows. Those options are enabled/disabled per architecture, and I bet you are using a 32 bit Windows and a 64 bit Linux FPC binary. It's quite possible that some that are not shown for x86-64 while they should be though. At least they're shown for the 32-bit version on linux Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] dward debug info - someone promiced more compact debug info than stabs
On 16 Mar 2010, at 16:41, Paul Ishenin wrote: But 200 Mb of info for 10Mb executable is too much. How do you think? I personally don't care at all. I don't believe that other compilers on windows generates so fat output for dwarf. Do you know any similar numbers for gcc? No, since I don't use Windows. It's hard to compare with Mac OS X, because there a) the DWARF debug info is not linked into the final binary, it just remains in the original object files (and the application contains references to the object files) b) you can use a (closed source) utility called dsymutil that goes through all object files of a program, collects the DWARF information, removes the duplicate information and then generates an external file that contains the unified debug information for the entire application GDB on Mac OS X can work with the debug information in both cases a) and b) Jonas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] dward debug info - someone promiced more compact debug info than stabs
On 16 Mar 2010, at 16:37, Flávio Etrusco wrote: On Tue, Mar 16, 2010 at 12:22 PM, Jonas Maebe > wrote: On 16 Mar 2010, at 15:58, Paul Ishenin wrote: Why dwarf information has so big debug files (comparing with stabs) on windows? Because Windows (just like Darwin) does not support referring to DWARF debug info from one object file to another, so a lot of debug information is duplicated in multiple units. Out of curiosity, is this a limitation of gdb, the library loader, or the dwarf/library format? On Mac OS X, it's a limitation of the linker (done on purpose, to making linking much faster and less memory intensive). I don't know about Windows. Jonas___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] dward debug info - someone promiced more compact debug info than stabs
16.03.2010 22:33, Jonas Maebe wrote: Why dwarf information has so big debug files (comparing with stabs) on windows? Because Windows (just like Darwin) does not support referring to DWARF debug info from one object file to another, so a lot of debug information is duplicated in multiple units. We also encode more information when using DWARF than when using Stabs (e.g. properties, absolute variables, public/private/protected information, calling convention, virtuality of methods). But 200 Mb of info for 10Mb executable is too much. How do you think? I don't believe that other compilers on windows generates so fat output for dwarf. Do you know any similar numbers for gcc? Best regards, Paul Ishenin. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] dward debug info - someone promiced more compact debug info than stabs
On Tue, Mar 16, 2010 at 12:22 PM, Jonas Maebe wrote: > > On 16 Mar 2010, at 15:58, Paul Ishenin wrote: > >> Why dwarf information has so big debug files (comparing with stabs) on >> windows? > > Because Windows (just like Darwin) does not support referring to DWARF debug > info from one object file to another, so a lot of debug information is > duplicated in multiple units. > > > Jonas Out of curiosity, is this a limitation of gdb, the library loader, or the dwarf/library format? Many thanks, Flávio ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] dward debug info - someone promiced more compact debug info than stabs
On 16 Mar 2010, at 16:22, Jonas Maebe wrote: On 16 Mar 2010, at 15:58, Paul Ishenin wrote: Why dwarf information has so big debug files (comparing with stabs) on windows? Because Windows (just like Darwin) does not support referring to DWARF debug info from one object file to another, so a lot of debug information is duplicated in multiple units. We also encode more information when using DWARF than when using Stabs (e.g. properties, absolute variables, public/private/protected information, calling convention, virtuality of methods). Jonas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] dward debug info - someone promiced more compact debug info than stabs
On 16 Mar 2010, at 15:58, Paul Ishenin wrote: Why dwarf information has so big debug files (comparing with stabs) on windows? Because Windows (just like Darwin) does not support referring to DWARF debug info from one object file to another, so a lot of debug information is duplicated in multiple units. Jonas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Missing command line parameters in Linux FPC
On 16 Mar 2010, at 08:44, Graeme Geldenhuys wrote: Under Linux the following information is missing, yet this information is displayed in the Windows version of FPC. It's unrelated to Linux vs Windows. Those options are enabled/disabled per architecture, and I bet you are using a 32 bit Windows and a 64 bit Linux FPC binary. It's quite possible that some that are not shown for x86-64 while they should be though. Jonas ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Missing command line parameters in Linux FPC
Hi, I looked at the FPC 2.4.1 output of the 'fpc -h' command and couldn't see any reference to the -W parameter. Under Linux the following information is missing, yet this information is displayed in the Windows version of FPC. - -W Target-specific options (targets) -WbCreate a bundle instead of a library (Darwin) -WBCreate a relocatable image (Windows) -WCSpecify console type application (EMX, OS/2, Windows) -WDUse DEFFILE to export functions of DLL or EXE (Windows) -WeUse external resources (Darwin) -WFSpecify full-screen type application (EMX, OS/2) -WGSpecify graphic type application (EMX, OS/2, Windows) -WiUse internal resources (Darwin) -WNDo not generate relocation code, needed for debugging (Windows) -WRGenerate relocation code (Windows) -WXEnable executable stack (Linux) - I know most of these options are not related to Linux (though there is one option now), I still think it's appropriate to output this information with the Linux FPC executable, because most FPC projects are cross-platform, so it is handy to see all available help for all platforms. Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/ ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] dward debug info - someone promiced more compact debug info than stabs
Hello, FPC developers' list Why dwarf information has so big debug files (comparing with stabs) on windows? lazarus.exe: 11MB lazarus.dbg: 219Mb As I remember with stabs I had something about 100MB for debug info. And as I remember dwarf debug info must be less fat as stabs. Best regards, Paul Ishenin. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] RTL and Unicode filenames operations.
Any hints about the package? http://bugs.freepascal.org/view.php?id=15795 thanks, dmitry ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
