std: Use Android LFS off64_t, ftruncate64, and lseek64#31805
Merged
bors merged 1 commit intorust-lang:masterfrom Feb 22, 2016
Merged
std: Use Android LFS off64_t, ftruncate64, and lseek64#31805bors merged 1 commit intorust-lang:masterfrom
bors merged 1 commit intorust-lang:masterfrom
Conversation
Android should use 64-bit LFS symbols for `lseek` and `ftruncate`, lest those offset parameters suffer a lossy cast down to a 32-bit `off_t`. Unlike GNU/Linux, Android's `stat`, `dirent`, and related functions are always 64-bit LFS compatible, and `open` already implies `O_LARGEFILE`, so all those don't need to follow Linux. It might be nice to unify them anyway, but those other LFS symbols aren't present in API 18 bionic. r? @alexcrichton
Member
Collaborator
|
⌛ Testing commit 7e96216 with merge 24a2984... |
Collaborator
|
💔 Test failed - auto-mac-32-opt |
Member
Author
|
Hmm, mac-32 timed out on |
Member
|
@bors: retry On Sun, Feb 21, 2016 at 4:13 PM, Josh Stone notifications@github.com
|
Collaborator
bors
added a commit
that referenced
this pull request
Feb 22, 2016
Android should use 64-bit LFS symbols for `lseek` and `ftruncate`, lest those offset parameters suffer a lossy cast down to a 32-bit `off_t`. Unlike GNU/Linux, Android's `stat`, `dirent`, and related functions are always 64-bit LFS compatible, and `open` already implies `O_LARGEFILE`, so all those don't need to follow Linux. It might be nice to unify them anyway, but those other LFS symbols aren't present in API 18 bionic. r? @alexcrichton
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Android should use 64-bit LFS symbols for
lseekandftruncate, lestthose offset parameters suffer a lossy cast down to a 32-bit
off_t.Unlike GNU/Linux, Android's
stat,dirent, and related functions arealways 64-bit LFS compatible, and
openalready impliesO_LARGEFILE,so all those don't need to follow Linux. It might be nice to unify them
anyway, but those other LFS symbols aren't present in API 18 bionic.
r? @alexcrichton