On 8/31/2012 23:46, K. Frank wrote: > There is a memory-exhausted issue with building recent versions of Qt with > recent versions of mingw-w64. I don't know whose "fault" it is -- my guess > is that there is an inefficiency in mingw-w64 that is triggered by the large > size of Qt. I've been able to work around it, but it is a nuisance. >
It has nothing to do with mingw-w64 itself, the trigger itself is the inlined dllexport code and the way C++/GCC handles it. As I understand, these inlined code is expanded and duplicated for EVERY object, so it bloats up the linker memory use. A workaround is to tell GCC not to inline any code that is marked for dllexport. Personally, I don't see why you would inline a code that is marked dllexport. Inline is not always faster, especially with giant cache size these days, why thrash the CPU cache just to avoid a function call overhead?
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
