Does a 32-bit VM mean that no individual primitives can have an
argument or return value greater than 32 bits?  File-size is something
that, in 2012 with HD video recording devices, can very easily exceed
32-bits so it would seem to be overkill for ALL objects to have to be
larger than 32 bits (as in a 64-bit VM) just for this one primitive..


On Thu, Mar 15, 2012 at 11:45 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> On Thu, Mar 15, 2012 at 10:35:47PM -0500, Chris Muller wrote:
>> I have a 3.2GB file, but Squeak reports its #fileSize as 0 (in the
>> DirectoryEntry).  It seems to occur for any file that large.
>>
>> Is it an overflow condition in the VM?  Is it possible to fix?
>
> It works fine with an interpreter VM compiled in 64-bit mode. I
> cannot look into it in detail now, but an educated guess is that
> it relates to the definition of size_t for 32-bit programs, and
> that for the kind of work you are doing here a 64-bit VM may be
> in order.
>
> Dave
>