From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111025 invoked by alias); 3 Apr 2015 02:37:51 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 110978 invoked by uid 48); 3 Apr 2015 02:37:47 -0000 From: "hp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/54005] Use __atomic_always_lock_free in libstdc++ is_lock_free instead of __atomic_is_lock_free Date: Fri, 03 Apr 2015 02:37:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 4.8.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hp at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: bkoz at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-04/txt/msg00187.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54005 --- Comment #16 from Hans-Peter Nilsson --- (In reply to Jonathan Wakely from comment #14) > Can we close this? No. IIUC, we're still/again using __atomic_is_lock_free with alignment deduced from the current object rather than the type (even though it's now a proxy-object; the faked pointer is constructed from the alignment of the current object). So, r221701 was wrong to change from null to the alignment-deduced fake-pointer.