On Friday, October 20, 2017 6:52:11 PM PDT Jordan Justen wrote:
> I'm now doubting the uninitialized padding explanation. I tried the
> memset in the glsl_struct_field constructor as Ken mentioned, but I
> also tried adding initializers for the fields in the default
> constructor, and it fixed valgrind.
>
> I didn't find anything mentioning that a default constructor on a c++
> struct requires the fields to be explicitly initialized. I would think
> that each field would be default initialized, the same as for a c++
> class.
>
> Anyway, here is alternate patch that fixes valgrind. Is this
> preferable to a memset in the constructor? Is either Reviewed-by
> worthy?
>
> diff --git a/src/compiler/glsl_types.h b/src/compiler/glsl_types.h
> index b5e97e638b..0b4a66ca4d 100644
> --- a/src/compiler/glsl_types.h
> +++ b/src/compiler/glsl_types.h
> @@ -1045,6 +1045,13 @@ struct glsl_struct_field {
> }
>
> glsl_struct_field()
> + : type(NULL), name(NULL), location(0), offset(0), xfb_buffer(0),
> + xfb_stride(0), interpolation(0), centroid(0),
> + sample(0), matrix_layout(0), patch(0),
> + precision(0), memory_read_only(0),
> + memory_write_only(0), memory_coherent(0), memory_volatile(0),
> + memory_restrict(0), image_format(0), explicit_xfb_buffer(0),
> + implicit_sized_array(0)
> {
> /* empty */
> }
>
> -JordanThis looks good to me, initializing members in the constructor is very reasonable. I like this better. Reviewed-by: Kenneth Graunke <kenn...@whitecape.org>
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
