https://bugs.kde.org/show_bug.cgi?id=469079
--- Comment #2 from Igor Kushnir <igor...@gmail.com> --- (In reply to Eugene Shalygin from comment #0) > Parsing fails with clang 16 and GCC 13 when GCC is selected as "Compiler for > path". clang complains on these types being undefined: _Float32, _Float64, > _Float128, _Float32x, _Float64x, _Float128x. This is with the C++20 mode set > by CMake, haven't tried other standards. What are the practical consequences/problems? What workaround do you employ for this bug? Does anyone know how to fix this issue properly? Milian fixed similar issues in two different ways: https://commits.kde.org/kdevelop/ce41c99ba3cc67acd931b784e1c029f16cb1641e https://commits.kde.org/kdevelop/35ea746ddd49e872998152cc157152c2cb5b86ea Is there a Clang command-line argument that enables these _Float* types? Or do we have to resort to injecting a preprocessor definition of each unknown type to its alternative spelling, or even to some other similar type if no such alternative spelling is supported by Clang? -- You are receiving this mail because: You are watching all bug changes.
