On 10 October 2016 at 22:43, Axel Davy wrote:
> On 10/10/2016 12:44, Emil Velikov wrote:
>>
>> On 6 October 2016 at 18:51, Axel Davy wrote:
>>>
>>> On systems with more than 4GB of ram,
>>> os_get_total_physical_memory was triggering an integer
>>> overflow for the linux and haiku path, when on
>
On 10/10/2016 12:44, Emil Velikov wrote:
On 6 October 2016 at 18:51, Axel Davy wrote:
On systems with more than 4GB of ram,
os_get_total_physical_memory was triggering an integer
overflow for the linux and haiku path, when on
32 bits.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=9456
On 6 October 2016 at 18:51, Axel Davy wrote:
> On systems with more than 4GB of ram,
> os_get_total_physical_memory was triggering an integer
> overflow for the linux and haiku path, when on
> 32 bits.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94561
>
> Signed-off-by: Axel Davy
>
Reviewed-by: Marek Olšák
Marek
On Thu, Oct 6, 2016 at 7:51 PM, Axel Davy wrote:
> On systems with more than 4GB of ram,
> os_get_total_physical_memory was triggering an integer
> overflow for the linux and haiku path, when on
> 32 bits.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id
On systems with more than 4GB of ram,
os_get_total_physical_memory was triggering an integer
overflow for the linux and haiku path, when on
32 bits.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=94561
Signed-off-by: Axel Davy
---
src/gallium/auxiliary/os/os_misc.c | 4 ++--
1 file chan