This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of NAD Future status.
Section: 99 [filesys.ts::fs.filesystem.synopsis], 99 [filesys.ts::fs.op.file_size] Status: NAD Future Submitter: CH-8 Opened: 2014-01-20 Last modified: 2016-08-10
Priority: Not Prioritized
View all other issues in [filesys.ts::fs.filesystem.synopsis].
View all issues with NAD Future status.
uintmax_t is specified to hold at least 64 bit. This is not enough for sizes beyond 4 [sic] exabytes.
Specify whether an implementation must provide a uintmax_t that can hold the maximum possible space and file size values.
[2014-02-06: Jeffery Yasskin points out 64-bits unsigned actually has a maximum value of "16 exabytes, not 4"]
[2014-02-07: Beman Dawes suggests: This should be NAD. Such ultra-large files are the province of enterprise-wide filesystems such as requested by IBM and others for a follow-on SG3 TS. That would be the best vehicle to address this concern IMO.]
[ 2014-02-11 Issaquah: NAD Future. ]