On Tue, Apr 10, 2018 at 1:50 PM, Rob Clark wrote:
> On Tue, Apr 10, 2018 at 1:17 PM, Jason Ekstrand wrote:
>> On Tue, Apr 10, 2018 at 9:59 AM, Rob Clark wrote:
>>>
>>> On Tue, Apr 10, 2018 at 11:55 AM, Jason Ekstrand
>>> wrote:
>>> > On Tue, Apr 10, 2018 at 8:17 AM, Rob Clark wrote:
>>> >>
>>>
On Tue, Apr 10, 2018 at 1:17 PM, Jason Ekstrand wrote:
> On Tue, Apr 10, 2018 at 9:59 AM, Rob Clark wrote:
>>
>> On Tue, Apr 10, 2018 at 11:55 AM, Jason Ekstrand
>> wrote:
>> > On Tue, Apr 10, 2018 at 8:17 AM, Rob Clark wrote:
>> >>
>> >> On Tue, Apr 10, 2018 at 11:04 AM, Jason Ekstrand
>> >>
On Tue, Apr 10, 2018 at 9:59 AM, Rob Clark wrote:
> On Tue, Apr 10, 2018 at 11:55 AM, Jason Ekstrand
> wrote:
> > On Tue, Apr 10, 2018 at 8:17 AM, Rob Clark wrote:
> >>
> >> On Tue, Apr 10, 2018 at 11:04 AM, Jason Ekstrand
> >> wrote:
> >> > On Tue, Apr 10, 2018 at 6:20 AM, Rob Clark
> wrote:
On Tue, Apr 10, 2018 at 11:55 AM, Jason Ekstrand wrote:
> On Tue, Apr 10, 2018 at 8:17 AM, Rob Clark wrote:
>>
>> On Tue, Apr 10, 2018 at 11:04 AM, Jason Ekstrand
>> wrote:
>> > On Tue, Apr 10, 2018 at 6:20 AM, Rob Clark wrote:
>> >>
>> >> On Mon, Apr 9, 2018 at 10:52 PM, Jason Ekstrand
>> >>
On Tue, Apr 10, 2018 at 8:17 AM, Rob Clark wrote:
> On Tue, Apr 10, 2018 at 11:04 AM, Jason Ekstrand
> wrote:
> > On Tue, Apr 10, 2018 at 6:20 AM, Rob Clark wrote:
> >>
> >> On Mon, Apr 9, 2018 at 10:52 PM, Jason Ekstrand
> >> wrote:
> >> > + A bunch of potentially interested parties.
> >> >
>
On Tue, Apr 10, 2018 at 11:04 AM, Jason Ekstrand wrote:
> On Tue, Apr 10, 2018 at 6:20 AM, Rob Clark wrote:
>>
>> On Mon, Apr 9, 2018 at 10:52 PM, Jason Ekstrand
>> wrote:
>> > + A bunch of potentially interested parties.
>> >
>> > On Mon, Apr 9, 2018 at 4:25 PM, Caio Marcelo de Oliveira Filho
>
On Tue, Apr 10, 2018 at 6:20 AM, Rob Clark wrote:
> On Mon, Apr 9, 2018 at 10:52 PM, Jason Ekstrand
> wrote:
> > + A bunch of potentially interested parties.
> >
> > On Mon, Apr 9, 2018 at 4:25 PM, Caio Marcelo de Oliveira Filho
> > wrote:
> >>
> >> Hi,
> >>
> >> > typedef struct {
> >> > -
On Mon, Apr 9, 2018 at 10:52 PM, Jason Ekstrand wrote:
> + A bunch of potentially interested parties.
>
> On Mon, Apr 9, 2018 at 4:25 PM, Caio Marcelo de Oliveira Filho
> wrote:
>>
>> Hi,
>>
>> > typedef struct {
>> > - nir_parameter_type param_type;
>> > - const struct glsl_type *type;
>> >
+ A bunch of potentially interested parties.
On Mon, Apr 9, 2018 at 4:25 PM, Caio Marcelo de Oliveira Filho <
caio.olive...@intel.com> wrote:
> Hi,
>
> > typedef struct {
> > - nir_parameter_type param_type;
> > - const struct glsl_type *type;
> > + uint8_t num_components;
> > + uint8_t
Hi,
> typedef struct {
> - nir_parameter_type param_type;
> - const struct glsl_type *type;
> + uint8_t num_components;
> + uint8_t bit_size;
> } nir_parameter;
(...)
> @@ -683,18 +692,12 @@ validate_tex_instr(nir_tex_instr *instr, validate_state
> *state)
> static void
> validate_c
This commit completely reworks function calls in NIR. Instead of having
a set of variables for the parameters and return value, nir_call_instr
now has simply has a number of sources which get mapped to load_param
intrinsics inside the functions. It's up to the client API to build an
ABI on top of
11 matches
Mail list logo