Harald van Dijk comments

Results 35 comments of


                                            Harald van Dijk

__builtin_printf not diagnosed but results in invalid SPIR-V

> Hi @hvdijk, thanks for the report. > > I would close this as not a bug, because the C++ program you have is essentially ill-formed due to use of...

__builtin_printf not diagnosed but results in invalid SPIR-V

> It can https://registry.khronos.org/SPIR-V/specs/unified1/OpenCL.ExtendedInstructionSet.100.html#printf I stand corrected! You can see a remnant of what I originally included in my report, "either ... or an extension should be used", I took...

__builtin_printf not diagnosed but results in invalid SPIR-V

> @hvdijk is this behavior okay? Having it use an extension is fine, but it seems like the result still does not pass validation: > error: line 165: OpenCL.std printf:...

__builtin_printf not diagnosed but results in invalid SPIR-V

> At what point do you see this error message? When I run `spirv-val` like in my original message, using a fresh clone from current https://github.com/KhronosGroup/SPIRV-Tools

__builtin_printf not diagnosed but results in invalid SPIR-V

This looks like it's fixed to me, though the previously generated invalid SPIR-V was (IIRC) accepted by the Intel OpenCL driver, the newly generated valid SPIR-V results in errors there....