Re: 64-bit G5?

From: Adam Warner (usenet_at_consulting.net.nz)
Date: 10/07/03 

Date: Tue, 07 Oct 2003 17:33:28 +1300

Hi Christopher Browne,

>> Apple's core market is in Video, Photographic image manipulation, and
>> DTP. For these uses, 64 bit is only about allowing larger memory
>> address spaces per process, and the G5 lets you do that now.
>
> Hmm? From what I saw in Duane's comments, this isn't something that
> MacOS-X supports, G5 or no. If they aren't supporting 64 bit pointers,
> by default, then you have NOT got "larger memory address spaces per
> process."

I'm speculating here that Raffael's comment may imply that Apple has moved
the kernel space above 4GB, permitting a full 4GB of address space for
32-bit applications, which could be an improvement of 1-2GB.

Regards,
Adam

Relevant Pages

  • Re: removing "virtual memory too low" message
    ... > I don't see the virtual memory error anymore on my system. ... > first registry entry takes care of it. ... > Regards. ... >> available physical memory to run more applications, ...
    (microsoft.public.windowsxp.embedded)
  • Re: xmalloc string functions
    ... require memory allocations depending on the way the system works. ... If the toolkit being used is not one of those, then it is irrelevant that some provide a means to do so, particularly if the "some" are not available for the platform being targeted. ... Not enough context for most real-world applications to recover at this point. ... At this point g_malloccalling abortbecomes a moot point, particularly if your auto-save code is robust against memory allocation errors. ...
    (comp.lang.c)
  • Re: ProDOS Plus
    ... operating system was not considered worth the problems when it was just as easy to make the applications support 128k or more ram. ... your suggested P-code system could do something similar by running in the aux 64k memory range $D000...FFFF or perhaps the aux ram used by the P8 /ram driver code space. ... the OS could fit in *only* the space that ProDOS now occupies. ... if practicality were a concern we probably wouldn't be using old hardware. ...
    (comp.sys.apple2)
  • Re: xmalloc string functions
    ... If these were the only choices (crashing applications or a frozen ... trying to malloc some rediculously large amount of memory - e.g. in the ... because their malloc wrapper decided to exit. ... Exiting on malloc failure makes sense for a utility like sort. ...
    (comp.lang.c)
  • Re: xmalloc string functions
    ... require memory allocations depending on the way the system works. ... Not enough context for most real-world applications to ... It is /more/ reliable to routinely auto-save the user's work (as you ... particularly if your auto-save code is robust against memory allocation ...
    (comp.lang.c)