On 10/24/2012 8:24 AM, Steve Davies wrote: > On 23 October 2012 18:56, Zan Lynx <zl...@acm.org> wrote: >> On Fri, 2012-10-19 at 14:24 +0100, Steve Davies wrote: >>> As a result, Pan is limited to the memory addressable by a 32-bit >>> application, which is 2Gb under windows. (32 bits allows 4Gb to be >>> addressed, but 32 bit apps only get 2Gb for a number of reasons which >>> I would not explain well) >> >> If you build your app with the LARGEADDRESSAWARE flag then it can use >> all 4GB of virtual space. Of course there are some possible bugs you can >> run into and if you're using third-party libraries you may not be able >> to fix them. >> >> Check here for some details: >> http://stackoverflow.com/questions/5185406/how-does-the-large-address-aware-flag-work-for-32-bit-applications-on-64-bit-com >> http://msdn.microsoft.com/ja-jp/isv/bb190527%28l=en-us%29 >> > > From a cursory read of those pages: > > 1) It assumes a Microsoft development environment against MS .dll files > 2) It assumes you are writing the code-base with MS in mind. > > Neither of these are true. Pan is a Linux product being compiled with > GCC and linked to libraries with GCCs linker. Many of the libraries > (.dll and static) are pre-compiled, and will have no clue about > Microsoft's LARGEADDRESSAWARE flag.
For MinGW it is --large-address-aware given to the "ld" linker. From the search results I read, MinGW support libraries will work fine since their code is almost entirely from Unix where addresses > 2GB have been common. _______________________________________________ Pan-users mailing list Pan-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/pan-users
