Eli Zaretskii <e...@gnu.org> writes: > DJ, would the following semi-kludgey workaround be acceptable?
It would be no worse than what we have now, if the only purpose is to avoid a warning. Ideally, we would check to see if we're discarding non-zero values from that offset, and not call the callback with known bogus data. I suppose the usefulness of that depends on how often you'll encounter 4Gb+ xcoff64 files on mingw32 ?
