[Mingw-w64-public] cross multilib binutils
The wiki page tells us that in order to compile a multilib binutils one have to add --enable-targets=... I'm not quite sure if that is necessary. I've just compiled my own without that option, and I have no problem compiling mingw-w64-crt with both architectures. -- chs -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] cross multilib binutils
On 4/23/2012 14:34, Christer Solskogen wrote: The wiki page tells us that in order to compile a multilib binutils one have to add --enable-targets=... I'm not quite sure if that is necessary. I've just compiled my own without that option, and I have no problem compiling mingw-w64-crt with both architectures. binutils has changed recently to emulate 32bit targets if 64bit is default, not sure if this is true for 32bit default targets. signature.asc Description: OpenPGP digital signature -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] Too big size of the executable file
Hello list.
I use MinGW by MinGW-builds project[1].
When I compiled this little code: int main() {return 0;}
with this command line: gcc main.c -omain -s -O2
I get the .exe file with size ~33 Kb. I think that this size is too big.
I know that MinGW-builds project uses CRT from mingw-w64 project,
that's why I write in this mailing-list.
Tell me please, is this a normal size? What can be done to reduce the size?
Thanks.
[1] http://sourceforge.net/projects/mingwbuilds/
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Too big size of the executable file
Hello Alex,
2012/4/20 Alex D:
Hello list.
I use MinGW by MinGW-builds project[1].
When I compiled this little code: int main() {return 0;}
with this command line: gcc main.c -omain -s -O2
I get the .exe file with size ~33 Kb. I think that this size is too big.
I know that MinGW-builds project uses CRT from mingw-w64 project,
that's why I write in this mailing-list.
Tell me please, is this a normal size? What can be done to reduce the size?
Thanks.to help
I can confirm that a smallest default executable build for 32-bit is
about 33.792 bytes in size. This size is caused by startup-code. You
can customize startup-code here, if you know that some features (like
eg pseudo-relocation) aren't required. By this you can save for sure
about 12k in size. But as standard startup has to support anything,
which might be used, it is a bit bigger as required in such a simple
case.
You can shrinken it size by specifying to linker specific PE
section/field-alignments (or using here for example hpux compression
tool). This can reduce this executable about some kB, too.
If you are interested in optimization of our startup-code to produce
smallest necessary code-size, be welcome to contribute to us.
Regards,
Kai
PS: Please subscribe first to this ML before posting to it
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Patch for incorrect references to pVtbl
Hello Stefan, well 316 kb patch is pretty huge ... so I walked throught it and committed it at rev 4962, Please try to keep patch in general not that big. about maximal 80kb are more handy for review ;) Thanks, Kai -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] Patch for incorrect references to pVtbl
On 4/23/12, Kai Tietz ktiet...@googlemail.com wrote: Hello Stefan, well 316 kb patch is pretty huge ... so I walked throught it and committed it at rev 4962, Please try to keep patch in general not that big. about maximal 80kb are more handy for review ;) Thanks, Kai I merged r4961+4962 into v2.x branch, hopefully without errors as of r4963: please test. I think the relevant bug entries can be closed. -- O.S. -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
