The reason high bits are often set is because an address layout
is actually 4 indicies into the page table and a page byte
offset. So all the way to bit 48 there is index info the cpu uses.
On Monday, 9 October 2023 at 05:57:47 UTC, Richard (Rikki) Andrew
Cattermole wrote:
As far as I'm aware, no cpu that you can get ahold of support
more than 48bit of address space at the hardware level.
There is simply no reason at this time to support more, due to
the fact that nobody has
As far as I'm aware, no cpu that you can get ahold of support more than
48bit of address space at the hardware level.
There is simply no reason at this time to support more, due to the fact
that nobody has implemented anywhere near that maximum.
Also worth noting, the address a block of
https://dlang.org/library/core/bitop/bsr.html
I'm trying to find out allocated object's address' space:
```
import std.stdio;
import core.bitop;
void main() {
const size_t ONE_G = 1 << 30;
char[][128] ptrs;
foreach (i, ref ptr; ptrs) {
ptr = new char[ONE_G];
if (ptr is null) {
