[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2020-11-13 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2020-11-09 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #27 from Mark Wielaard --- (In reply to Paul Floyd from comment #22) > I want to keep the prereq because in theory someone could be building with a > very old GCC that does not support -fsized-deallocation. And you were correct :) (In

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2020-11-09 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #26 from Paul Floyd --- Created attachment 133174 --> https://bugs.kde.org/attachment.cgi?id=133174=edit Fix gmake check on Solaris -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2020-11-09 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 Paul Floyd changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2020-11-08 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #24 from Mark Wielaard --- (In reply to Paul Floyd from comment #23) > Created attachment 133151 [details] > Update patch to cover both x86 and amd64 Looks good to me. I believe the sized_delete.stderr.exp file should match not just amd64

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2020-11-08 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 Paul Floyd changed: What|Removed |Added Attachment #130196|0 |1 is obsolete|

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2020-11-07 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #22 from Paul Floyd --- Filtering out the free was enough to get the test to pass on the 3 OSes that I tested on [Linux, Solaris and FreeBSD]. You are right that it is not necessary for the test, and I'll add malloc to the filter. I want

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2020-11-07 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=372347 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #21 from Mark

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2020-07-17 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #20 from Paul Floyd --- Created attachment 130196 --> https://bugs.kde.org/attachment.cgi?id=130196=edit Patch to test this support -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2018-05-29 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #19 from Paul Floyd --- I think that -fsized-deallocation would be better as it’s more specific. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2018-05-29 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #18 from Philippe Waroquiers --- (In reply to Paul Floyd from comment #17) > Great. I also have a small test case for this, but it uses a Makefile rather > than the Valgrind perl mechanism. I'll look into adapting it to the Valgrind >

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2018-05-29 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #17 from Paul Floyd --- Great. I also have a small test case for this, but it uses a Makefile rather than the Valgrind perl mechanism. I'll look into adapting it to the Valgrind infrastructure. -- You are receiving this mail because: You

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2018-05-29 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=372347 Philippe Waroquiers changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2018-05-27 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #15 from Romain Geissler --- Yes I am using it already, and it's working. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2018-05-26 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #14 from Paul Floyd --- Can you test the patch attached here? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2018-05-16 Thread Romain Geissler
https://bugs.kde.org/show_bug.cgi?id=372347 Romain Geissler changed: What|Removed |Added CC|

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2017-06-28 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #12 from Paul Floyd --- Are you having issues with C++14 or C++17? I have a patch for C++14. I need to do a bit more work to get my regression tests for it into the Valgrind format. For the C++17, it looks like a lot more

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2017-06-27 Thread rcmgleite
https://bugs.kde.org/show_bug.cgi?id=372347 rcmgleite changed: What|Removed |Added CC||r.cmgle...@gmail.com ---

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-12-27 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #10 from Paul Floyd --- Created attachment 103028 --> https://bugs.kde.org/attachment.cgi?id=103028=edit Patch for C++14 sized delete operators Added operator[] overloads. Tested on Solaris 32 and 64bit, Linux 32 and 64

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-12-27 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 Paul Floyd changed: What|Removed |Added Attachment #102909|0 |1 is obsolete|

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-12-20 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #9 from Paul Floyd --- Created attachment 102909 --> https://bugs.kde.org/attachment.cgi?id=102909=edit Patch to add C++14 sized delete overloads Tested on Solaris 32bit and 64bit, Linux 64 bit (don't currently have 32bit

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-12-20 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 Paul Floyd changed: What|Removed |Added Attachment #102906|0 |1 is obsolete|

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-12-20 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #7 from Paul Floyd --- Created attachment 102906 --> https://bugs.kde.org/attachment.cgi?id=102906=edit Patch to add C++14 sized delete overloads Tested on Solaris. ==9916== ERROR SUMMARY: 0 errors from 0 contexts

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-12-20 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=372347 Paul Floyd changed: What|Removed |Added CC||pa...@free.fr --- Comment #6 from

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-11-13 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #5 from Philippe Waroquiers --- (In reply to Christopher Smith from comment #4) > (In reply to Philippe Waroquiers from comment #3) > > If your new/delete operators will have the 'normal/expected' semantic, >

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-11-13 Thread Christopher Smith
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #4 from Christopher Smith --- (In reply to Philippe Waroquiers from comment #3) > If your new/delete operators will have the 'normal/expected' semantic, > then why would the Valgrind replacement create a problem ? > Or,

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-11-13 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #3 from Philippe Waroquiers --- (In reply to Christopher Smith from comment #2) > Thanks for the reply. > > If you plan on making Valgrind override my delete operator as well, that > could cause issues for my

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-11-13 Thread Christopher Smith
https://bugs.kde.org/show_bug.cgi?id=372347 --- Comment #2 from Christopher Smith --- Thanks for the reply. If you plan on making Valgrind override my delete operator as well, that could cause issues for my intermediate code. One thing I could do, would be to use the Client

[valgrind] [Bug 372347] Replacement problem of the additional c++14/c++17 new and delete operators

2016-11-13 Thread Philippe Waroquiers
https://bugs.kde.org/show_bug.cgi?id=372347 Philippe Waroquiers changed: What|Removed |Added Summary|Redirecting new but not