public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64735] std::future broken on armel
Date: Fri, 23 Jan 2015 10:25:00 -0000 [thread overview]
Message-ID: <bug-64735-4-c5FRljk7QH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64735-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|libstdc++ |c++
--- Comment #4 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> i.e. it's not broken, it's missing, and that's by design.
Right so if I parse that correctly, it boils down to implementation of atomics
with calls to kernel helper function vs the lack of it IIUC. Not really a
libstdc++ issue but more of an issue with the way in which atomics are
implemented on arch's that don't have the actual instruction support but are
implemented through kernel helper functions.
It appears as though this breaks quite a few packages on older versions of the
architecture so that's interesting.
Ramana
next prev parent reply other threads:[~2015-01-23 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 21:21 [Bug libstdc++/64735] New: " bastiaan at bjacques dot org
2015-01-23 10:05 ` [Bug libstdc++/64735] " redi at gcc dot gnu.org
2015-01-23 10:05 ` redi at gcc dot gnu.org
2015-01-23 10:25 ` ramana at gcc dot gnu.org [this message]
2015-01-23 12:33 ` [Bug c++/64735] " bastiaan at bjacques dot org
2015-01-23 15:51 ` redi at gcc dot gnu.org
2021-04-15 16:10 ` [Bug libstdc++/64735] " cvs-commit at gcc dot gnu.org
2021-07-22 17:05 ` cvs-commit at gcc dot gnu.org
2021-07-22 21:29 ` cvs-commit at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-64735-4-c5FRljk7QH@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).