[Vm-dev] [unix[ Large file support (was: StandardFileStream size
John M McIntosh
johnmci at smalltalkconsulting.com
Thu Jun 14 14:14:39 UTC 2012
No you have to back a decade when I implemented these. The 64 bit file calls are not part of the generic standard unix headers across all platforms so Ian choose to make them optional so the vm will compile on the least capable platform.
Sent from my iPhone
On Jun 14, 2012, at 9:59 AM, "David T. Lewis" <lewis at mail.msen.com> wrote:
> On Thu, Jun 14, 2012 at 02:59:12PM +0200, Bert Freudenberg wrote:
>> On 2012-06-14, at 14:29, David T. Lewis wrote:
>>> I just double checked, and it turns out that it is not true that the standard
>>> interpreter VM works. The interpreter VM works for large files when compiled as
>>> a 64-bit executable, and it works when compiled as a 32-bit executable your
>>> instructions for the LFS flags are followed. But the officially distributed
>>> 32-bit interpreter VM does not have LFS support enabled, and if you open a file
>>> list on very large file, the file size will not be displayed correctly.
>> Ah, okay. So I guess it would be a Good Idea to enable LFS in the interpreter too, right? There shouldn't be bad side effects.
> Presumably yes. Although I don't know if there might be some performance
> tradeoffs involved in using 64 bit file addresses. But my guess would be
> that Linux uses 32-bit file addresses in 32-bit mode to accomodate older
> programs that assume 32-bit file references. Maybe Eliot can comment?
>> - Bert -
>> PS: Don't give me too much credit. These are not "my" instructions, I just found and posted them :)
> Well, *I* certainly would not have figured it out any time soon ;-)
More information about the Vm-dev