all devices regression report - 2018-01-15-13:17:11 - afe8e5468db1f875432aa711676eaf4007d13daa

[email protected] Mon, 15 Jan 2018 13:17:11 -0800 (PST)

Newsgroups	gmane.comp.printing.ghostscript.regression
Message-ID	<20180115211711.EC241204025E@i7>

Differences in all devices errors using gs/examples files

Previous Revision: b199f558834d0fbd365cccc426eed0fdc3e035c7
 Current Revision: afe8e5468db1f875432aa711676eaf4007d13daa

commit afe8e5468db1f875432aa711676eaf4007d13daa
Author:     Ray Johnston <[email protected]>
AuthorDate: Mon Jan 15 08:14:02 2018 -0800
CommitDate: Mon Jan 15 09:44:38 2018 -0800

    Fix opening of files > 2GB on Windows built with VS after VS2013
    
    For whatever reason, even on 64 bit builds, Visual Studio changed
    behaviour and the compiler/run-time now invoke __fstat64i32 for
    fstat. This returns an error if the file size can't fit in int32
    (the older fstat just returned a negative number, ignoring overflow)
    Change to use __fstat64 which works on VS 2005 so it should be
    fine. I also tested this build on an ancient Dell with 760Mb RAM
    running Windows XP SP3 and it runs fine, so __fstat64 is not a
    problem going back that far.

base/stat_.h

new errors:

errors that went away:

errors that are not whitelisted:
=== ghostpdl/examples/transparency_example.ps === bjc880j ===
=== ghostpdl/examples/transparency_example.ps === cp50 ===
=== ghostpdl/examples/transparency_example.ps === escpage ===
=== ghostpdl/examples/transparency_example.ps === lips2p ===
=== ghostpdl/examples/transparency_example.ps === lips3 ===
=== ghostpdl/examples/transparency_example.ps === lips4 ===
=== ghostpdl/examples/transparency_example.ps === npdl ===
=== ghostpdl/examples/transparency_example.ps === psdrgb ===