[Bug libstdc++/64735] std::future broken on armel

2021-07-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 --- Comment #16 from CVS Commits --- The releases/gcc-9 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:ba5e10a8c84f56bb2838adb6d1cc9b74741ac4f1 commit r9-9640-gba5e10a8c84f56bb2838adb6d1cc9b74741ac4f1 Author: Jonathan

[Bug libstdc++/64735] std::future broken on armel

2021-07-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 --- Comment #15 from CVS Commits --- The releases/gcc-10 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:f2074277aa3ce0848429e34d6149ba26ff3b708e commit r10-9997-gf2074277aa3ce0848429e34d6149ba26ff3b708e Author: Jonathan

[Bug libstdc++/64735] std::future broken on armel

2021-04-15 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 --- Comment #14 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:6c0c7fc6236470a533675cd3cd1ebb1cc3dd112c commit r11-8198-g6c0c7fc6236470a533675cd3cd1ebb1cc3dd112c Author: Jonathan Wakely

[Bug libstdc++/64735] std::future broken on armel

2017-01-18 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 Jonathan Wakely changed: What|Removed |Added CC||rafal at rawicki dot org --- Comment

[Bug libstdc++/64735] std::future broken on armel

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

[Bug libstdc++/64735] std::future broken on armel

2017-01-04 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 --- Comment #11 from Jonathan Wakely --- Author: redi Date: Wed Jan 4 10:54:59 2017 New Revision: 244051 URL: https://gcc.gnu.org/viewcvs?rev=244051=gcc=rev Log: Support exception propagation without lock-free atomic int 2017-01-04 Pauli

[Bug libstdc++/64735] std::future broken on armel

2016-11-12 Thread doko at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 Matthias Klose changed: What|Removed |Added CC||doko at gcc dot gnu.org --- Comment

[Bug libstdc++/64735] std::future broken on armel

2016-11-09 Thread suokkos at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 --- Comment #9 from Pauli --- atomicity.h uses exactly same builtins if _GLIBCXX_ATOMIC_BUILTINS is set 1. Difference include check for __gthread_active_p check and annotations for race detector. Annotations are empty macros in default build.

[Bug libstdc++/64735] std::future broken on armel

2016-11-07 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 Jonathan Wakely changed: What|Removed |Added Status|NEW |ASSIGNED Component|c++

[Bug libstdc++/64735] std::future broken on armel

2015-01-23 Thread ramana at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 Ramana Radhakrishnan ramana at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW

[Bug libstdc++/64735] std::future broken on armel

2015-01-23 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 --- Comment #2 from Jonathan Wakely redi at gcc dot gnu.org --- I think this is expected, the std:future type and std::async function are declared unconditionally, but the definitions are guarded by: #if defined(_GLIBCXX_HAS_GTHREADS)

[Bug libstdc++/64735] std::future broken on armel

2015-01-23 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735 --- Comment #3 from Jonathan Wakely redi at gcc dot gnu.org --- i.e. it's not broken, it's missing, and that's by design.