public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/65913] [5 Regression] Linking failure without -latomic Date: Thu, 08 Oct 2015 16:55:00 -0000 [thread overview] Message-ID: <bug-65913-4-6gZP3WbxWL@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 --- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> --- Author: redi Date: Thu Oct 8 16:54:23 2015 New Revision: 228615 URL: https://gcc.gnu.org/viewcvs?rev=228615&root=gcc&view=rev Log: Backport PR libstdc++/65913 fix from mainline. Handle alignment in __atomic_is_lock_free gcc: 2015-09-17 Richard Henderson <rth@redhat.com> PR libstdc++/65913 * builtins.c (fold_builtin_atomic_always_lock_free): Handle fake pointers that encode the alignment of the object. libstdc++-v3: 2015-09-17 Jonathan Wakely <jwakely@redhat.com> PR libstdc++/65913 * include/bits/atomic_base.h (__atomic_base<_TTp>::is_lock_free(), __atomic_base<_PTp*>::is_lock_free()): Call the built-in with the immediate pointer value, not a variable. * include/std/atomic (atomic<T>::is_lock_free()): Likewise. * testsuite/29_atomics/atomic/65913.cc: New. Added: branches/gcc-5-branch/libstdc++-v3/testsuite/29_atomics/atomic/65913.cc Modified: branches/gcc-5-branch/gcc/ChangeLog branches/gcc-5-branch/gcc/builtins.c branches/gcc-5-branch/libstdc++-v3/ChangeLog branches/gcc-5-branch/libstdc++-v3/include/bits/atomic_base.h branches/gcc-5-branch/libstdc++-v3/include/std/atomic
prev parent reply other threads:[~2015-10-08 16:55 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 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 [this message]
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-6gZP3WbxWL@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: linkBe 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).