This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/64735] std::future broken on armel
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 23 Jan 2015 10:04:57 +0000
- Subject: [Bug libstdc++/64735] std::future broken on armel
- Auto-submitted: auto-generated
- References: <bug-64735-4 at http dot gcc dot gnu dot org/bugzilla/>
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) && defined(_GLIBCXX_USE_C99_STDINT_TR1) \
&& (ATOMIC_INT_LOCK_FREE > 1)
If your target doesn't meet those conditions then you don't get to use
std::future