Re-enable mmap on 32-bit architectures #2000
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
memmap2 v0.3.0 introduced a regression when trying to map files larger than 4GB on 32-bit architectures which was subsequently fixed in v0.3.1.
This commit bumps locked version of the memmap2 dependency to the current v0.5.0 and reverts fdfc418 to re-enable mmap on 32-bit architectures as a different approach to fixing #1911.
This was tested to report matches from the end of a 5GB file using MinGW and Wine:
whereas still using memmap2 v0.3.0 but fdfc418 reverted would silently fail