On Tue, Mar 13, 2018 at 8:33 AM, Emil Velikov
wrote:
> On 13 March 2018 at 15:02, Jason Ekstrand wrote:
> > On Tue, Mar 13, 2018 at 7:56 AM, Emil Velikov
> > wrote:
> >>
> >> On 12 March 2018 at 08:40, Iago Toral Quiroga
> wrote:
> >> > af5f2322d0c64 addressed this for extension commands, but
On 13 March 2018 at 15:02, Jason Ekstrand wrote:
> On Tue, Mar 13, 2018 at 7:56 AM, Emil Velikov
> wrote:
>>
>> On 12 March 2018 at 08:40, Iago Toral Quiroga wrote:
>> > af5f2322d0c64 addressed this for extension commands, but the spec
>> > mandates
>> > this behavior also for core API commands.
On Tue, Mar 13, 2018 at 7:56 AM, Emil Velikov
wrote:
> On 12 March 2018 at 08:40, Iago Toral Quiroga wrote:
> > af5f2322d0c64 addressed this for extension commands, but the spec
> mandates
> > this behavior also for core API commands. From the Vulkan spec,
> > Table 2. vkGetDeviceProcAddr behavi
On 12 March 2018 at 08:40, Iago Toral Quiroga wrote:
> af5f2322d0c64 addressed this for extension commands, but the spec mandates
> this behavior also for core API commands. From the Vulkan spec,
> Table 2. vkGetDeviceProcAddr behavior:
>
> device pnamereturn
>
On Mon, 2018-03-12 at 07:37 -0700, Jason Ekstrand wrote:
> On Mon, Mar 12, 2018 at 1:40 AM, Iago Toral Quiroga m> wrote:
> > af5f2322d0c64 addressed this for extension commands, but the spec
> > mandates
> >
> > this behavior also for core API commands. From the Vulkan spec,
> >
> > Table 2. vkG
On Mon, Mar 12, 2018 at 1:40 AM, Iago Toral Quiroga
wrote:
> af5f2322d0c64 addressed this for extension commands, but the spec mandates
> this behavior also for core API commands. From the Vulkan spec,
> Table 2. vkGetDeviceProcAddr behavior:
>
> device pnamereturn