On Wed, 2017-05-03 at 09:40 -0700, Jason Ekstrand wrote:
> On Fri, Apr 28, 2017 at 1:34 AM, Juan A. Suarez Romero
> wrote:
> > On Thu, 2017-04-27 at 20:36 -0700, Jason Ekstrand wrote:
> > > On Thu, Apr 27, 2017 at 9:23 AM, Juan A. Suarez Romero
> > >
On Wed, May 3, 2017 at 9:40 AM, Jason Ekstrand wrote:
> On Fri, Apr 28, 2017 at 1:34 AM, Juan A. Suarez Romero <
> jasua...@igalia.com> wrote:
>
>> On Thu, 2017-04-27 at 20:36 -0700, Jason Ekstrand wrote:
>>
>> On Thu, Apr 27, 2017 at 9:23 AM, Juan A. Suarez Romero <
>>
On Fri, Apr 28, 2017 at 1:34 AM, Juan A. Suarez Romero
wrote:
> On Thu, 2017-04-27 at 20:36 -0700, Jason Ekstrand wrote:
>
> On Thu, Apr 27, 2017 at 9:23 AM, Juan A. Suarez Romero <
> jasua...@igalia.com> wrote:
>
> On Wed, 2017-04-26 at 07:35 -0700, Jason Ekstrand wrote:
>
On Thu, 2017-04-27 at 20:36 -0700, Jason Ekstrand wrote:
> On Thu, Apr 27, 2017 at 9:23 AM, Juan A. Suarez Romero
> wrote:
> > On Wed, 2017-04-26 at 07:35 -0700, Jason Ekstrand wrote:
> >
> > > We should only use size_t when referring to sizes of bits of CPU memory.
> >
>
On Thu, Apr 27, 2017 at 9:23 AM, Juan A. Suarez Romero
wrote:
> On Wed, 2017-04-26 at 07:35 -0700, Jason Ekstrand wrote:
> > We should only use size_t when referring to sizes of bits of CPU memory.
> > Anything on the GPU or just a regular array length should be a type that
On Wed, 2017-04-26 at 07:35 -0700, Jason Ekstrand wrote:
> We should only use size_t when referring to sizes of bits of CPU memory.
> Anything on the GPU or just a regular array length should be a type that
> has the same size on both 32 and 64-bit architectures. For state
> objects, we use a
We should only use size_t when referring to sizes of bits of CPU memory.
Anything on the GPU or just a regular array length should be a type that
has the same size on both 32 and 64-bit architectures. For state
objects, we use a uint32_t because we'll never allocate a piece of
driver-internal GPU