From: Samuel Pitoiset <samuel.pitoiset@gmail.com>
To: Francisco Jerez <currojerez@riseup.net>,
Hans de Goede <hdegoede@redhat.com>,
mesa-dev@lists.freedesktop.org
Cc: nouveau@lists.freedesktop.org
Subject: Re: [Nouveau] [PATCH mesa] clover: Fix pipe_grid_info.indirect not being initialized
Date: Mon, 14 Mar 2016 21:52:29 +0100 [thread overview]
Message-ID: <56E7248D.3020204@gmail.com> (raw)
In-Reply-To: <87lh5k4wen.fsf@riseup.net>
On 03/14/2016 09:49 PM, Francisco Jerez wrote:
> Samuel Pitoiset <samuel.pitoiset@gmail.com> writes:
>
>> On 03/14/2016 02:29 PM, Samuel Pitoiset wrote:
>>>
>>>
>>> On 03/14/2016 02:26 PM, Hans de Goede wrote:
>>>> Hi,
>>>>
>>>> On 14-03-16 14:01, Samuel Pitoiset wrote:
>>>>>
>>>>>
>>>>> On 03/14/2016 01:50 PM, Hans de Goede wrote:
>>>>>> After pipe_grid_info.indirect was introduced, clover was not modified
>>>>>> to set it causing it to pass uninitialized memory for it to
>>>>>> launch_grid.
>>>>>>
>>>>>> This commit fixes this by zero-ing the entire pipe_grid_info struct
>>>>>> when
>>>>>> declaring it, to avoid similar problems popping-up in the future.
>>>>>>
>>>>>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>>>>> ---
>>>>>> src/gallium/state_trackers/clover/core/kernel.cpp | 2 +-
>>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>>
>>>>>> diff --git a/src/gallium/state_trackers/clover/core/kernel.cpp
>>>>>> b/src/gallium/state_trackers/clover/core/kernel.cpp
>>>>>> index 8396be9..dad66aa 100644
>>>>>> --- a/src/gallium/state_trackers/clover/core/kernel.cpp
>>>>>> +++ b/src/gallium/state_trackers/clover/core/kernel.cpp
>>>>>> @@ -55,7 +55,7 @@ kernel::launch(command_queue &q,
>>>>>> const auto reduced_grid_size =
>>>>>> map(divides(), grid_size, block_size);
>>>>>> void *st = exec.bind(&q, grid_offset);
>>>>>> - struct pipe_grid_info info;
>>>>>> + struct pipe_grid_info info = { 0, };
>>>>>
>>>>> Right, good catch, it's my fault.
>>>>>
>>>>> = { 0 }; is enough btw.
>>>>
>>>> I prefer to add the "," to make clear that we are initializing the
>>>> entire struct,
>>>> I read it as ", ...".
>>>
>>> Well, usually we use { 0 } in mesa, try to grep and you will see. :-)
>>> There is only 3 occurrences of { 0, }, but I think they are quite old.
>>
>> Of course, I'm not really against this ",", but I just want consistency
>> with the other parts.
>>
>
> In C++ '{}' is standard, more concise, and works for a wider range of
> types regardless of their layout ('{ 0 }' is valid or not depending on
> what the first member of the struct is, while '{}' works regardless, in
> C++11 it can even be used to initialize non-POD types with custom
> constructors), so it should be generally preferred instead.
>
> Don't bother to resend just because of my nitpicking, I'll fix it up
> before I push the last revision of your change, which is:
I didn't know that, thanks for this very good explanation. :-)
>
> Reviewed-by: Francisco Jerez <currojerez@riseup.net>
>
>>>
>>>>
>>>>> This should be backported to mesa 11.2 I guess, could you please send
>>>>> a v2 with this minor fix and add the cc thing?
>>>>
>>>> Sure, as soon as we're done bikeshedding on the "," :)
>>>>
>>>> Regards,
>>>>
>>>> Hans
>>>
>>
>> --
>> -Samuel
>> _______________________________________________
>> Nouveau mailing list
>> Nouveau@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/nouveau
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
prev parent reply other threads:[~2016-03-14 20:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 12:50 [PATCH mesa] clover: Fix pipe_grid_info.indirect not being initialized Hans de Goede
2016-03-14 13:01 ` Samuel Pitoiset
[not found] ` <56E6B629.8080708-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-14 13:26 ` Hans de Goede
[not found] ` <56E6BBFC.2020306-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-14 13:29 ` Samuel Pitoiset
[not found] ` <56E6BCD2.5000002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-14 13:31 ` Samuel Pitoiset
[not found] ` <56E6BD32.5000203-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-14 20:49 ` Francisco Jerez
2016-03-14 20:52 ` Samuel Pitoiset [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56E7248D.3020204@gmail.com \
--to=samuel.pitoiset@gmail.com \
--cc=currojerez@riseup.net \
--cc=hdegoede@redhat.com \
--cc=mesa-dev@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.