On 28.09.2014, at 11:12, Matt Oliver <protogo...@gmail.com> wrote: > On 28 September 2014 18:49, Reimar Döffinger <reimar.doeffin...@gmx.de> > wrote: > >> On Sun, Sep 21, 2014 at 10:17:15AM +0100, Reimar Döffinger wrote: >>> Allows 32 bit version of FFmpeg to use up to 4 GB of RAM >>> instead of just 2 GB on Windows if the OS can provide it. >> >> Any other comments? >> Note the documentation for that option: >>> The /LARGEADDRESSAWARE option tells the linker that the application can >>> handle addresses larger than 2 gigabytes. >> This flag is _only_ used to signal that an application can deal >> with addresses that use more than 31 address bits. >> I.e. it is only for those horribly misdesigned programs that >> thought "oh, let's store some extra stuff in that unused high bit >> of the address". Which FFmpeg definitely does not. >> There is no indication that ptrdiff_t limitations or similar have >> any relevance to whether one should set this or not. >> > > There shouldnt be any problem with this at all as it basically just sets a > flag in the output dll/exe (which can be manually set after compilation > anyway). > > LARGEADDRESSAWARE should probably be added for msvc/icl as well.
Patch welcome. I don't want to add things I can't easily test. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
