News for hackers. Stuff that matters.
Re:The Itanic Saga: The History of VLIW and Itanium by lstodd on Wednesday January 24, 2024 @06:10AM (#39115976)
No it could not not have happened.

Address space pressure was immense back in the day, and plain doubling the width of everything while retaining the compatablity was the obvious choice.

Re:The Itanic Saga: The History of VLIW and Itanium by aleph_minus_one on Wednesday January 24, 2024 @08:28AM (#39117042)
> Address space pressure was immense back in the day, and plain doubling the width of everything while retaining the compat[i]blity was the obvious choice.

PAE (https://en.wikipedia.org/wiki/Physical_Address_Extension) existed for quite some time to enable x86-32 processors to access > 4 GiB of RAM. Thus, I would argue that if the OS provided some functionality to move allocated pages in and out of the 32 bit address space of a process to enable the process to use more than 4 GiB of memory is a much more obvious choice.

Re:The Itanic Saga: The History of VLIW and Itanium by acdha on Wednesday January 24, 2024 @09:28AM (#39117694)
PAE got some use - for that “each process gets 4GB” model you mentioned in Darwin and Linux - but it was slower and didn’t allow individual processes to easily use more than 2-3GB in practice.
Re:The Itanic Saga: The History of VLIW and Itanium by lstodd on Friday February 02, 2024 @10:28AM (#39229693)
> Thus, I would argue that if the OS provided some functionality to move allocated pages in and out of the 32 bit address space of a process to enable the process to use more than 4 GiB of memory ...

Oh, no. Back then the segmented memory model was still remembered and no one wanted a return to that. PAE wasn't seen as anything but a bandaid.

Everyone wanted big flat address space. And we got it. Because it was the obvious choice, and the silicon could support it, Intel or no.