public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/11157] __block is a reserved word with clang -fblocks
Date: Thu, 21 Nov 2013 22:06:00 -0000 [thread overview]
Message-ID: <bug-11157-131-14iLSLJcgp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11157-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=11157
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
Resolution|WONTFIX |FIXED
--- Comment #10 from Carlos O'Donell <carlos at redhat dot com> ---
Fixed.
commit 84ae135d3282dc362bed0a5c9a575319ef336884
Author: Meador Inge <meadori@codesourcery.com>
Date: Thu Nov 21 16:57:37 2013 -0500
Use __glibc_block in public headers.
As detailed in PR11157, the use of '__block' is known to interfere
with keywords in some environments, such as the Clang -fblocks extension.
Recently a similar issue was raised concerning the use of '__unused'
and a '__glibc' prefix was proposed to create a glibc implementation
namespace for these sorts of issues [1]. This patches takes that
approach.
[1] https://sourceware.org/ml/libc-alpha/2012-02/msg00047.html
[2] http://lists.debian.org/debian-glibc/2013/11/msg00020.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-11-21 22:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11157-131@http.sourceware.org/bugzilla/>
2011-12-27 2:42 ` mark at heily dot com
2012-06-13 18:51 ` ppluzhnikov at google dot com
2012-08-08 8:22 ` lubos at dolezel dot info
2012-08-08 8:51 ` bonzini at gnu dot org
2013-11-21 22:06 ` carlos at redhat dot com [this message]
2014-06-30 20:24 ` fweimer at redhat dot com
2010-01-10 17:52 [Bug libc/11157] New: " truls dot becken at gmail dot com
2010-01-15 7:35 ` [Bug libc/11157] " drepper at redhat dot com
2010-01-25 21:36 ` truls dot becken at gmail dot com
2010-04-04 18:33 ` drepper at redhat dot com
2010-04-06 23:31 ` Tanktalus at gmail dot com
2010-06-08 7:40 ` bonzini at gnu dot org
2010-06-08 8:03 ` bonzini at gnu dot 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-11157-131-14iLSLJcgp@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).