19 Aug
2026
19 Aug
'26
1:38 p.m.
Peter Dimov said:
The reason for this is because you also need binary-format=pe. But this should be fixed elsewhere; you shouldn't need to supply these by hand.
Now what I'm wondering is what about the CPU architecture? How does it assume the best format for the program? PE32 has a memory limit of 4GB in a Windows NT process when compiled for a 32-bit machine, which a 64-bit PE32+ image does not have. I've been wondering about dropping this flag and just providing `pe32plus`, and `pe32`, with `pe` alias to the `pe32` flag by default. Best, - Amlal