[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-09-15 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=469079 Igor Kushnir changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In|

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-08-19 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=469079 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-31 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #14 from Eugene Shalygin --- > So there is no fatal error in a single-file project? Are the "unknown type > name" errors printed somewhere? > > /usr/include/stdlib.h:141:8: error: unknown type name '_Float32' I see errors in the terminal w

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-30 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #13 from Igor Kushnir --- > There is the following block for each _Float type in the > /usr/include/bits/floatn-common.h file: > # if !__GNUC_PREREQ (7, 0) || (defined __cplusplus && !__GNUC_PREREQ (13, > 0)) > typedef float _Float16 __attr

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-30 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #12 from Eugene Shalygin --- The issue has not went away with update to GCC 13.2, so I sat down to create an MWE only to discover that the problem is not directly controlled by the C++20 mode. There is the following block for each _Float t

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-28 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #11 from Eugene Shalygin --- I'm building GCC 13.2, once it's ready I create an MWE, or maybe the update resolves the issue. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-28 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #10 from Igor Kushnir --- (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,

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-27 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #9 from Igor Kushnir --- (In reply to Igor Kushnir from comment #8) > KDevelop should probably typedef _Float128 to double, not __float128, to > match GCC's defines. Or rather to "long double": > typedef long double _Float64x; -- You are r

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-27 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #8 from Igor Kushnir --- From https://codebrowser.dev/gcc/include/x86_64-linux-gnu/bits/floatn-common.h.html: > No configurations support _Float128x or, as of GCC 7, have compiler > support for a type meeting the requirements for _Float128x.

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-27 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #7 from Igor Kushnir --- (In reply to Eugene Shalygin from comment #5) > Yes, definitely. Everything works fine in the C++17 mode. Strange. Will have to investigate this. > I haven't tried clang-15, but why would it work if the newer versio

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-27 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #6 from Eugene Shalygin --- Although the same GCC page states "These types are not supported when compiling C++." I don't understand what's going on then. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-27 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #5 from Eugene Shalygin --- (In reply to Igor Kushnir from comment #4) > The failing KDevelop's tests use a default standard and C++14, so the issue > isn't limited to C++20. Does the standard version make a difference in your > case? Yes,

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-27 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #4 from Igor Kushnir --- (In reply to Eugene Shalygin from comment #3) > Well, the IDE ceases to work as soon as you turn the C++20 mode on. As a > workaround I provide those types as typedefs in the Language support/Defines > page of the pr

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-27 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #3 from Eugene Shalygin --- (In reply to Igor Kushnir from comment #2) > What are the practical consequences/problems? What workaround do you employ > for this bug? Well, the IDE ceases to work as soon as you turn the C++20 mode on. As a w

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-07-25 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #2 from Igor Kushnir --- (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, _

[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1

2023-04-27 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=469079 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushn