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: "ramana 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:01:35 +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
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-01-23
CC| |ramana at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |4.9.0, 4.9.1, 4.9.2, 5.0
--- Comment #1 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
Confirmed with -march=armv5te on all platforms. The only thing I can think of
off the top of my head that is different for armv5te compared to armv7-a is
that on armv5te we end up going through the kernel helper function for all
atomic and sync type operations, there is no inlining and maybe that's what is
broken in some sense here.
Would help for some comments from a libstdc++ / C++ person.