https://bugs.freedesktop.org/show_bug.cgi?id=93188
--- Comment #5 from Emil Velikov ---
(In reply to Ian Romanick from comment #4)
> I guess the question is whether or not this builds with Visual Studio's C++
> compiler. If not, maybe we should reopen with changes to
https://bugs.freedesktop.org/show_bug.cgi?id=93188
--- Comment #6 from Jason Ekstrand ---
I had a patch at one point to help C++ out here. I ended up not sending it out
because it only fixed warnings that only came up if you had extra warnings
turned on. basically it
https://bugs.freedesktop.org/show_bug.cgi?id=93188
--- Comment #4 from Ian Romanick ---
I guess the question is whether or not this builds with Visual Studio's C++
compiler. If not, maybe we should reopen with changes to the summary?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=93188
--- Comment #3 from Jose Fonseca ---
Though we still might want to avoid non-standard C++ constructs regardless.
C++ is not a superset of C99 (though some portions are widely supported), so
NIR needs to take care when
https://bugs.freedesktop.org/show_bug.cgi?id=93188
Jose Fonseca changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=93188
--- Comment #1 from Alan Coopersmith ---
The Studio C++ compiler does not support C99 compound literals - when I raised
this to the Studio C++ team they said:
> This:
> (nir_src) { init }
>
> is a C99 feature
https://bugs.freedesktop.org/show_bug.cgi?id=93188
Bug ID: 93188
Summary: "nir/nir.h", line 552: Error: Unexpected type name
"nir_src" encountered.
Product: Mesa
Version: git
Hardware: x86 (IA32)
OS: