[Bug libstdc++/82481] dangling reference in mutex:693

2021-01-13 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 --- Comment #13 from CVS Commits --- The releases/gcc-8 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:283c218a4846075c549f0215d6883e577b26e845 commit r8-10726-g283c218a4846075c549f0215d6883e577b26e845 Author: Jonathan Wakel

[Bug libstdc++/82481] dangling reference in mutex:693

2021-01-13 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 --- Comment #12 from CVS Commits --- The releases/gcc-9 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:4aeae11db66c9bce0aadf447e6ff0776a97bfccf commit r9-9180-g4aeae11db66c9bce0aadf447e6ff0776a97bfccf Author: Jonathan Wakely

[Bug libstdc++/82481] dangling reference in mutex:693

2021-01-13 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 --- Comment #11 from CVS Commits --- The releases/gcc-10 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:8d3636923a309074eb19240ebaa30c1a0801eaaf commit r10-9267-g8d3636923a309074eb19240ebaa30c1a0801eaaf Author: Jonathan Wake

[Bug libstdc++/82481] dangling reference in mutex:693

2017-10-20 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 Jonathan Wakely changed: What|Removed |Added Target Milestone|8.0 |7.3 --- Comment #10 from Jonathan Wake

[Bug libstdc++/82481] dangling reference in mutex:693

2017-10-20 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 --- Comment #9 from Jonathan Wakely --- Author: redi Date: Fri Oct 20 15:14:33 2017 New Revision: 253944 URL: https://gcc.gnu.org/viewcvs?rev=253944&root=gcc&view=rev Log: PR libstdc++/82481 Suppress clang-tidy warnings Backport from mainline 2

[Bug libstdc++/82481] dangling reference in mutex:693

2017-10-13 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/82481] dangling reference in mutex:693

2017-10-13 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 --- Comment #7 from Jonathan Wakely --- Author: redi Date: Fri Oct 13 12:39:24 2017 New Revision: 253724 URL: https://gcc.gnu.org/viewcvs?rev=253724&root=gcc&view=rev Log: PR libstdc++/82481 Suppress clang-tidy warnings PR libstdc++/824

[Bug libstdc++/82481] dangling reference in mutex:693

2017-10-11 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 Jonathan Wakely changed: What|Removed |Added Status|RESOLVED|ASSIGNED Last reconfirmed|

[Bug libstdc++/82481] dangling reference in mutex:693

2017-10-10 Thread heinzisoft at web dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 --- Comment #5 from heinzisoft at web dot de --- (In reply to Jonathan Wakely from comment #2) > It is a dangling pointer, but it can't be dereferenced, so it doesn't matter. > > It's only used by std::call_once and will be set to a different loc

[Bug libstdc++/82481] dangling reference in mutex:693

2017-10-10 Thread heinzisoft at web dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 --- Comment #4 from heinzisoft at web dot de --- (In reply to Jonathan Wakely from comment #3) > (In reply to heinzisoft from comment #0) > > Building the following minimal example with libstdc++ 7.0.1 > > And why are you using that unsupported v

[Bug libstdc++/82481] dangling reference in mutex:693

2017-10-09 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/82481] dangling reference in mutex:693

2017-10-09 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 --- Comment #2 from Jonathan Wakely --- It is a dangling pointer, but it can't be dereferenced, so it doesn't matter. It's only used by std::call_once and will be set to a different local variable by the next call. We could zero the pointer, but

[Bug libstdc++/82481] dangling reference in mutex:693

2017-10-08 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82481 Markus Trippelsdorf changed: What|Removed |Added CC||trippels at gcc dot gnu.org --- Co