__VA_OPT__ was documented after 7.3.0 and the eprintf example for it
ends with two backslashes instead of one:
https://gcc.gnu.org/onlinedocs/cpp/Variadic-Macros.html
Regards,
Bogdan
, it doesn't have any registers.
Instead it's using IDs for everything [1]. I didn't find a way to create IDs
instead of registers in GCC.
3. SPIR-V supports some "non-standard" types[2], will it be a problems to
support these types in GCC frontend/backend?
Cheers,
Bo
On Wednesday, March 4, 2015 5:22 PM, David Malcolm wrote:
On Wed, 2015-03-04 at 14:36 +, BogDan wrote:
> Hello folks,
>
>
> Probably is a little bit too early, but I'd like to ask if there is
> any chance to use gcc to produce SPIR-V [1].
> It will be just great if
fantastic to use only one compiler collection for CPU and for GPU
compute&graphics!
Cheers,
BogDan.
[1] https://www.khronos.org/registry/spir-v/
