[Bug libstdc++/84323] call_once uses TLS even when once_flag is set

2020-11-03 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84323 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/84323] call_once uses TLS even when once_flag is set

2020-11-03 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84323 --- Comment #4 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:93e79ed391b9c636f087e6eb7e70f14963cd10ad commit r11-4691-g93e79ed391b9c636f087e6eb7e70f14963cd10ad Author: Jonathan Wakely Date:

[Bug libstdc++/84323] call_once uses TLS even when once_flag is set

2020-11-03 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84323 Jonathan Wakely changed: What|Removed |Added Target Milestone|--- |11.0 Status|NEW

[Bug libstdc++/84323] call_once uses TLS even when once_flag is set

2018-10-31 Thread antoshkka at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84323 --- Comment #3 from Antony Polukhin --- Just noted that libc++ already does this optimization: https://godbolt.org/z/alw1sq libc++ directly accesses the content of std::once_flag and skips all the thread local accesses if call_once previously

[Bug libstdc++/84323] call_once uses TLS even when once_flag is set

2018-02-12 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84323 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libstdc++/84323] call_once uses TLS even when once_flag is set

2018-02-12 Thread antoshkka at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84323 --- Comment #1 from Antony Polukhin --- Fixing this will also resolve Bug 55394, because there'll be no need in linking with pthread.