size of compiled exe in PB 6.11b3=6.10

[gurj]

win7x86
v6.11b3=250k
v6.10=253k
v6.01=75k

[Fred]

may be you were already using the VC linker because 250 kb is smaller than the minimal size used by polink (which is around 450kb).

[skywalk]

Code: Select all

~35k line threaded app compiled with 611b3.

app-cbe611b3vc.exe,    (MS link)              , 2424KB
app-cbe611b3.exe,      (PB link)              , 2439KB
app-cbe-o611b3vc.exe,  (MS link, no optimizer), 2661KB
app-cbe-o611b3.exe,    (PB link, no optimizer), 2674KB
app-asm611b3.exe,                             , 2781KB

Confirmed compiler selects MS VC link.exe if present.

[gurj]

thanks!
how to select link and optimizer?

[skywalk]

I prefer to use C compile with optimizer checked in the compiler options dialog.
You can also use a cmd line to compile your code and set the optimize switch.

The new PB linker is slightly faster than the MS VC link.exe and the resulting exe is only a small percentage larger.

Since it now installs with PB v611b3, there is no big reason to download and install MS VC link.exe.

[gurj]

thanks!
V6.11 has no difference between( C and without C, optimization and immersion). All is 250K.

[gurj]

Supplement: Confirm is to use lld-link.

[AZJIO]

gurj
Use 6.04 for small size and WindowsXP support.
Or 6.10 and higher for a size of 250kb and support Vista and higher.

As far as I understand there will be no return.

But I would like version 6.04 to be able to evolve a little for Windows (no Linux and no MacOS), since my programs are all within 50-200 kb. And as I understand it, this will not happen, because it will require double work.

[gurj]

In my impression, 6.02-6.04 there is a new issue on the path, so I only retain 6.01.

And the path old problems on the 6.10 inner path (such as include not supporting Chinese path).They have been completely solved!