[valgrind] [Bug 473677] make check compile failure with Clang 16 based on GCC 13.x

2023-08-25 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473677 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 473677] make check compile failure with Clang 16 based on GCC 13.x

2023-08-25 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473677 --- Comment #8 from Paul Floyd --- I'll try something like changing memcheck/test/Makefile.am from if HAVE_ALIGNED_CXX_ALLOC cxx17_aligned_new_SOURCES = cxx17_aligned_new.cpp cxx17_aligned_new_CXXFLAGS = -std=c++17 @FLAG_W_NO_MISMATCHED_NEW_DELETE@ si

[valgrind] [Bug 473677] make check compile failure with Clang 16 based on GCC 13.x

2023-08-25 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473677 --- Comment #7 from Paul Floyd --- That looks like the problem https://reviews.llvm.org/D8467 And clang++ -std=c++17 -fsized-deallocation -dM -E -x c++ /dev/null | grep sized #define __cpp_sized_deallocation 201309L -- You are receiving this mail b

[valgrind] [Bug 473677] make check compile failure with Clang 16 based on GCC 13.x

2023-08-25 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473677 --- Comment #6 from Paul Floyd --- It's possible that LLVM + libstdc++ disables sized delete. I'll try to find out some more. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 473677] make check compile failure with Clang 16 based on GCC 13.x

2023-08-25 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473677 --- Comment #5 from Paul Floyd --- (In reply to fanquake from comment #4) > > Can you confirm? I don't have easy access to clang 16 or gcc 13 on Linux. > > I'm still seeing build failures at dc6669cee7b557945fd41417bf531c7f5c9f1093: > > cxx17_aligned

[valgrind] [Bug 473677] make check compile failure with Clang 16 based on GCC 13.x

2023-08-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473677 --- Comment #4 from fanqu...@gmail.com --- > Can you confirm? I don't have easy access to clang 16 or gcc 13 on Linux. I'm still seeing build failures at dc6669cee7b557945fd41417bf531c7f5c9f1093: clang -Winline -Wall -Wshadow -Wno-long-long -g -fno-sta

[valgrind] [Bug 473677] make check compile failure with Clang 16 based on GCC 13.x

2023-08-24 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473677 --- Comment #3 from Paul Floyd --- Should be OK now. Can you confirm? I don't have easy access to clang 16 or gcc 13 on Linux. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 473677] make check compile failure with Clang 16 based on GCC 13.x

2023-08-24 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473677 --- Comment #2 from Paul Floyd --- I think that the testcase should be #include #include #include class alignas(64) MyClass { public: int i; }; class OrdinaryClass { public: int i; }; int main() { // unsized versions MyClass* myCl

[valgrind] [Bug 473677] make check compile failure with Clang 16 based on GCC 13.x

2023-08-23 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473677 --- Comment #1 from Paul Floyd --- Does it compile if you cast the second argument to size_t e.g., operator delete(myClass, static_cast(64U), std::align_val_t(64U)); A literal suffix would be nicer but size_t is only in C++23 (I believe https://open-s

[valgrind] [Bug 473677] make check compile failure with Clang 16 based on GCC 13.x

2023-08-23 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=473677 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr Assignee|jsew...@acm.