public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11157] __block is a reserved word with clang -fblocks
Date: Sun, 04 Apr 2010 18:33:00 -0000 [thread overview]
Message-ID: <20100404183253.27484.qmail@sourceware.org> (raw)
In-Reply-To: <20100110175229.11157.truls.becken@gmail.com>
------- Additional Comments From drepper at redhat dot com 2010-04-04 18:32 -------
(In reply to comment #2)
> By convention, double underscores are reserved for the compiler,
This is just plain wrong.
Compilers cannot just introduce new keywords, they have to live in many
environments. Therefore they have to be extra careful and use appropriate
prefixes etc. The llvm people don't care so why should anyone else?
--
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
http://sourceware.org/bugzilla/show_bug.cgi?id=11157
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-04-04 18:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[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
2014-06-30 20:24 ` fweimer at redhat dot com
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=20100404183253.27484.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).