Milos Nikic, le mar. 24 juin 2025 00:58:44 +0100, a ecrit:
> From: Milos Nikic
>
> The call to vm_object_print_part was passing 0ULL and ~0ULL
> for offset and size, respectively. These values are 64-bit
> (unsigned long long), which causes compiler warnings when
> building for 32-bit platforms w
Ah yes, good.
Damien
Sent from Proton Mail Android
Original Message
On 24/6/25 2:30 pm, Milos Nikic wrote:
> Hello,-
>
> On 32-bit systems, UINTPTR_MAX is 0x
>
> -
>
> On 64-bit systems, UINTPTR_MAX is 0x
>
> That is what we want, right?
>
> Also passi
Here is an example:
https://godbolt.org/z/fM8K5nGhx for 64 bits.
(didnt find a good option for 32 bit compiler there)
On Mon, Jun 23, 2025 at 9:29 PM Milos Nikic wrote:
>
> Hello,
>
>-
>
>On *32-bit systems*, UINTPTR_MAX is 0x
>-
>
>On *64-bit systems*, UINTPTR_MAX is 0x
Hello,
-
On *32-bit systems*, UINTPTR_MAX is 0x
-
On *64-bit systems*, UINTPTR_MAX is 0x
That is what we want, right?
Also passing anything larger than 0x (like ~0ULL) on a 32-bit build
causes *overflow and truncation*, and triggers warnings.
On Mon, Jun 23, 2025
But on 64 bit, isn't the value supposed to be sign extended to the full width
not uint32 max?
Damien
Sent from Proton Mail Android
Original Message
On 24/6/25 9:59 am, Milos Nikic wrote:
> From: Milos Nikic
>
> The call to vm_object_print_part was passing 0ULL and ~0UL
