No, there are two 47-bit halves. (But see my other comment about 57-bit address space.)
Re:The secret life of NaN
by cryptonector on Thursday April 05, 2018 @10:10PM
(#16770403)
Ay, sry.
I had this issue on both Solaris/SPARC and AIX/POWER because both use the full 64-bit address space. It required jumping through hoops to make sure the custom allocator could both allocate 1MB aligned pages that were also < 48 bits so that it would play nice with SpiderMonkey.
> There are two 48-bit halves. It could get bigger eventually.
Which is precisely why the implemented in that way, to prevent "clever" uses like this from eventually breaking on chipsets that define more address bits than the early default.
I remember Solaris had a problem because it would put anonymous mmap()s in one 48-bit range and the heap and stacks in the other range, and this broke some ECMAScript implementation that used NaN-coding with the assumption that all data would be in the top 48-bit address space.