On 21 September 2014 10:46:33 GMT+01:00, wm4 <nfx...@googlemail.com> wrote: >On Sun, 21 Sep 2014 10:17:15 +0100 >Reimar Döffinger <reimar.doeffin...@gmx.de> 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. >> >> Signed-off-by: Reimar Döffinger <reimar.doeffin...@gmx.de> >> --- >> configure | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/configure b/configure >> index 2c6db81..dec1cfc 100755 >> --- a/configure >> +++ b/configure >> @@ -3951,6 +3951,7 @@ case $target_os in >> enabled shared && ! enabled small && check_cmd $windres >--version && enable gnu_windres >> check_ldflags -Wl,--nxcompat >> check_ldflags -Wl,--dynamicbase >> + check_ldflags -Wl,--large-address-aware >> shlibdir_default="$bindir_default" >> SLIBPREF="" >> SLIBSUF=".dll" > >Is that really a good idea? ptrdiff_t can overflow in this case.
That would only apply if you could allocate more than 2GB in one allocation. Also it just makes Windows behave like Linux so it can't break anything not already broken on Linux. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
