Welcome, Guest. Please login or register.

Author Topic: IBM PPC970 64bit CPU at CeBIT  (Read 8264 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: IBM PPC970 64bit CPU at CeBIT
« on: March 13, 2003, 09:48:37 PM »
@lempkee

Hmm, lets put it this way:

There is allways a way to make FXPaint or so crawl  on
any HW. Done that with the native-x86-plugin and a 1.4GHZ CPU,
and can't say it was hard. Just take a big image and put it
through some heavy filters.  :-D
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: IBM PPC970 64bit CPU at CeBIT
« Reply #1 on: March 13, 2003, 10:04:30 PM »
@Hammer
That has nothing to do with OS itself (I'm just assuming
you haven't mad a cheap joke here .....).

64-FFS only means that it can handle bigger than 4GB (32) bit,
moving the OS to accept 64bit wide addresses would break
compability and is simply impossible for the existing apps.

A "boxed" design would be needed or some obscure page-swapping
like it had been done in MS-DOS .....
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else
 

Offline Kronos

  • Resident blue troll
  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 4017
    • Show all replies
    • http://www.SteamDraw.de
Re: IBM PPC970 64bit CPU at CeBIT
« Reply #2 on: March 14, 2003, 11:18:32 PM »
@crumb
Which won't be a prob solong you have "only" 4GB of RAM.

But imagine this:
A 32bit-app running in the lower 4GB.
A 64bit-app with data at 0x0000000100000000.

Those 2 want to communicate with each other ....

Mixing different address-sizes is not a good idea, and the
older version of Windows are a perfect proove for it.
1. Make an announcment.
2. Wait a while.
3. Check if it can actually be done.
4. Wait for someone else to do it.
5. Start working on it while giving out hillarious progress-reports.
6. Deny that you have ever announced it
7. Blame someone else