public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/65913] Linking failure without -latomic
Date: Wed, 20 May 2015 01:52:00 -0000 [thread overview]
Message-ID: <bug-65913-4-h4nrRh07oE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65913-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65913
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hp at gcc dot gnu.org
--- Comment #4 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to yan12125 from comment #3)
> Sorry, but I don't quite understand. Does that mean for all the future
> versions (5.2, 6.0, etc.) -latomic flag is necessary if
> atomic<T>::is_lock_free() is used in my program?
>From my reading of the comments, the patch and current svn sources, the answer
is "no". I'm guessing sooner or later the proposed patch will also be posted
to the gcc-patches@ list and promptly reviewed and committed. Then hopefully
back-ported in time for 5.2. But that's just a guess.
next prev parent reply other threads:[~2015-05-20 1:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 10:01 [Bug libstdc++/65913] New: " yan12125 at gmail dot com
2015-04-28 13:15 ` [Bug libstdc++/65913] " redi at gcc dot gnu.org
2015-04-28 16:01 ` rth at gcc dot gnu.org
2015-04-28 17:26 ` yan12125 at gmail dot com
2015-05-20 1:52 ` hp at gcc dot gnu.org [this message]
2015-07-13 12:20 ` redi at gcc dot gnu.org
2015-09-02 22:06 ` [Bug libstdc++/65913] [5/6 Regression] " redi at gcc dot gnu.org
2015-09-17 15:46 ` redi at gcc dot gnu.org
2015-09-17 15:48 ` [Bug libstdc++/65913] [5 " redi at gcc dot gnu.org
2015-10-08 16:55 ` redi 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-65913-4-h4nrRh07oE@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).