Re: [fpc-pascal] Why win64 program are considerably bigger in exe size than win 32?

2017-12-31 Thread Martok
Am 31.12.2017 um 11:15 schrieb Sven Barth via fpc-pascal: > Could/would you provide that tool as open source? Sure! I have attached the win32 binary as a release. > Does it only work with PE/COFF or also ELF?Since I only very crudely parse > the linker map

Re: [fpc-pascal] Why win64 program are considerably bigger in exe size than win 32?

2017-12-31 Thread Florian Klämpfl
Am 31.12.2017 um 00:19 schrieb Martok: > > And now the on-topic part: this compares an "empty" project (Lazarus: > Project->New->Program), compiled for win32 and win64 > > As you can see, the win64 image is about a third larger - but not so much > because of

Re: [fpc-pascal] Why win64 program are considerably bigger in exe size than win 32?

2017-12-31 Thread Mark Morgan Lloyd
On 31/12/17 00:15, Martok wrote: Oh, and I finally know why even simple LCL applications are so large: graphicsdrags in fcl-image, which includes full support for JPEG, TIFF, PNG and requirespasjpeg, paszlib and others. The widgetset indirection is surprisingly small. Interesting. -- Mark

Re: [fpc-pascal] Why win64 program are considerably bigger in exe size than win 32?

2017-12-31 Thread Sven Barth via fpc-pascal
Am 31.12.2017 00:19 schrieb "Martok" : Am 22.12.2017 um 09:30 schrieb Dennis: > I am upgrading my program from win 32 to win 64 using the new Lazarus 1.8. > I discovered my program exe size increased from 6M to 9M. Just for fun, I wrote a small program to parse Linker

Re: [fpc-pascal] Why win64 program are considerably bigger in exe size than win 32?

2017-12-30 Thread Martok
Am 22.12.2017 um 09:30 schrieb Dennis: > I am upgrading my program from win 32 to win 64 using the new Lazarus 1.8. > I discovered my program exe size increased from 6M to 9M. Just for fun, I wrote a small program to parse Linker Map files and show the image occupation by source object file

Re: [fpc-pascal] Why win64 program are considerably bigger in exe size than win 32?

2017-12-23 Thread Marco van de Voort
In our previous episode, leledumbo via fpc-pascal said: > > Why? > > At least pointer size takes double space, multiply it with every instances > 1.5x bigger is not impossible. For memory size, however the question was about binary size. And in instructions usually the full 64-bits of immediate

Re: [fpc-pascal] Why win64 program are considerably bigger in exe size than win 32?

2017-12-23 Thread Mark Morgan Lloyd
On 22/12/17 12:45, leledumbo via fpc-pascal wrote: Why? At least pointer size takes double space, multiply it with every instances1.5x bigger is not impossible. Particularly if the binary contains debugging information. -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions

Re: [fpc-pascal] Why win64 program are considerably bigger in exe size than win 32?

2017-12-22 Thread Graeme Geldenhuys
On 2017-12-22 08:30, Dennis wrote: I am upgrading my program from win 32 to win 64 using the new Lazarus 1.8. I discovered my program exe size increased from 6M to 9M. As already answered. The same applies to Linux and FreeBSD 64-bit programs. It's normal. Regards, Graeme -- fpGUI

Re: [fpc-pascal] Why win64 program are considerably bigger in exe size than win 32?

2017-12-22 Thread leledumbo via fpc-pascal
> Why? At least pointer size takes double space, multiply it with every instances 1.5x bigger is not impossible. -- Sent from: http://free-pascal-general.1045716.n5.nabble.com/ ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org

[fpc-pascal] Why win64 program are considerably bigger in exe size than win 32?

2017-12-22 Thread Dennis
I am upgrading my program from win 32 to win 64 using the new Lazarus 1.8. I discovered my program exe size increased from 6M to 9M. Why? Dennis ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org