64bit
Re: 64bit
+1
Re: 64bit
Please,please 64bit support!
Today already the processor no problem, rather the few memories the problem.
He would be sparing a hard disk.
Excuse me for the bad knowledges of English.
Today already the processor no problem, rather the few memories the problem.
He would be sparing a hard disk.
Excuse me for the bad knowledges of English.
Live8 Suite, Akai Apc40, 4*Uad1, RME9632, Adam A7
-
jean_pierre
- Posts: 38
- Joined: Thu Oct 25, 2007 5:20 am
Re: 64bit
quite a task to undertake, 64 bit.
in addition to the host application being able to address more memory, all reports of snowleopard have indicated that it will boot into a 64 bit kernel and frameworks on supported machinery (not core solo, et cetera), so launching a 32 bit version of live (as it currently is) will incur an additional penalty as the application will also need to load the 32 bit frameworks and libraries into memory, many of which may already be so, but their 64 bit brethren - further exascerbating memory pressure and perhaps being unfriendly to other running applications.
an area of contention might be plugin support, hosting a 32 bit plugin in a 64 bit application. this could be handled by moving plugin execution out of the application process into their own process and IPC'ing across the gap, plus use shared memory regions as necessary. this has the additional bonus of isolating plugin crashes from the host application.
in addition to the host application being able to address more memory, all reports of snowleopard have indicated that it will boot into a 64 bit kernel and frameworks on supported machinery (not core solo, et cetera), so launching a 32 bit version of live (as it currently is) will incur an additional penalty as the application will also need to load the 32 bit frameworks and libraries into memory, many of which may already be so, but their 64 bit brethren - further exascerbating memory pressure and perhaps being unfriendly to other running applications.
an area of contention might be plugin support, hosting a 32 bit plugin in a 64 bit application. this could be handled by moving plugin execution out of the application process into their own process and IPC'ing across the gap, plus use shared memory regions as necessary. this has the additional bonus of isolating plugin crashes from the host application.