public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51773] error building libitm/aatree.cc on ARM
Date: Fri, 06 Jan 2012 11:47:00 -0000	[thread overview]
Message-ID: <bug-51773-4-wr8vyTX9oJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51773-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51773

--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-01-06 11:47:15 UTC ---
On Fri, 6 Jan 2012, redi at gcc dot gnu.org wrote:

> does glibc also define macros for alignof, true, false, bool etc. in C++ mode?

Those C11 macros are defined in headers required to be provided by 
freestanding implementations, so provided by GCC, not glibc - but it was 
felt suitable to use assert.h for static_assert rather than creating a new 
stdstatic_assert.h header for that macro.  We already discussed C++ 
semantics for those headers, see 
<http://gcc.gnu.org/ml/gcc-patches/2011-11/msg00847.html>.


  parent reply	other threads:[~2012-01-06 11:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06  9:50 [Bug c++/51773] New: " vries at gcc dot gnu.org
2012-01-06 10:50 ` [Bug c++/51773] " redi at gcc dot gnu.org
2012-01-06 10:52 ` vries at gcc dot gnu.org
2012-01-06 10:56 ` redi at gcc dot gnu.org
2012-01-06 11:07 ` redi at gcc dot gnu.org
2012-01-06 11:47 ` joseph at codesourcery dot com [this message]
2012-01-06 12:08 ` redi at gcc dot gnu.org
2012-01-06 15:28 ` joseph at codesourcery dot com
2012-01-06 15:33 ` redi at gcc dot gnu.org
2012-01-06 15:44 ` jakub at gcc dot gnu.org
2012-01-06 15:51 ` joseph at codesourcery dot com
2012-01-06 16:12 ` jakub at gcc dot gnu.org
2012-01-09 11:35 ` vries 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-51773-4-wr8vyTX9oJ@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).