Date: Thu, 4 Sep 2025 08:31:23 +0200
> I do mean bytes, not bits.
> a function can return anything, what I was referencing is the fact that _BitInt(384) can not be used to access specialized registers, so a different type is required to do that.
> It can't because of 1. alignment requirements, even registers don't have alignment, the type must be swappable into memory.
Yeah, that "swapping" happens using load and store instructions that
operate on such a specialized register. Nothing prevents operations on
_BitInt(384) from being compiled down to such loads and stores.
> 2. That is not defined, making voodoo programing at best.
What is that even supposed to mean?!
> a function can return anything, what I was referencing is the fact that _BitInt(384) can not be used to access specialized registers, so a different type is required to do that.
> It can't because of 1. alignment requirements, even registers don't have alignment, the type must be swappable into memory.
Yeah, that "swapping" happens using load and store instructions that
operate on such a specialized register. Nothing prevents operations on
_BitInt(384) from being compiled down to such loads and stores.
> 2. That is not defined, making voodoo programing at best.
What is that even supposed to mean?!
Received on 2025-09-04 06:31:39