Hi Juha,
On Sun, 2016-02-07 at 23:37 +0200, Juha-Pekka Heikkilä wrote:
> Hi Iago,
>
> I know there are lot of places where there is malloc unchecked still
> -- and then there is ralloc which is a story of its own. Reason why I
> think checking these would be remotely useful in windows only (or
>
Hi,
On 08.02.2016 00:07, Matt Turner wrote:
On Sun, Feb 7, 2016 at 1:37 PM, Juha-Pekka Heikkilä
wrote:
I know there are lot of places where there is malloc unchecked still
-- and then there is ralloc which is a story of its own. Reason why I
think checking these
On 02/07/2016 02:07 PM, Matt Turner wrote:
> On Sun, Feb 7, 2016 at 1:37 PM, Juha-Pekka Heikkilä
> wrote:
>> Hi Iago,
>>
>> I know there are lot of places where there is malloc unchecked still
>> -- and then there is ralloc which is a story of its own. Reason why I
On Sun, Feb 7, 2016 at 1:37 PM, Juha-Pekka Heikkilä
wrote:
> Hi Iago,
>
> I know there are lot of places where there is malloc unchecked still
> -- and then there is ralloc which is a story of its own. Reason why I
> think checking these would be remotely useful in
Hi Iago,
I know there are lot of places where there is malloc unchecked still
-- and then there is ralloc which is a story of its own. Reason why I
think checking these would be remotely useful in windows only (or
other way around, not under linux kernel) is on Windows one can get
the null
I'm thinking these things maybe could be wrapped up inside something like
"#ifdef windows" or so in the future. At least for Android and Linux these
are normally quite useless.
/Juha-Pekka
Juha-Pekka Heikkila (2):
i965: in brw_link_shader() react to low memory
glsl: Check for null pointer at
Hi Juha,
I don't know why checking for this might be more relevant in Windows,
but in any case:
There are a ton of other places in mesa where we allocate memory via
calloc/malloc and we don't check that the allocation actually succeeded
so I am not sure that fixing a couple of instances of