From: Tim Song <t.canens.cpp@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Katsuhiko Nishimra <ktns.87@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>,
cfe-dev@lists.llvm.org
Subject: Re: [PATCH] libstdc++: Support std::is_aggregate on clang++ (was [cfe-dev] clang++: std::is_aggregate unusable with clang-5.0/libstdc++-7)
Date: Mon, 31 Jul 2017 17:23:00 -0000 [thread overview]
Message-ID: <CAPQZVxtfgh71eQcRLJHeqt3BEDu++PNmz5+e=PWbL9fmAOO5xg@mail.gmail.com> (raw)
In-Reply-To: <CAPQZVxuetVo6jnhBRZ37eW3yMrosMjyXHWMjTH6XdWaRC51Q9w@mail.gmail.com>
On Mon, Jul 31, 2017 at 11:13 AM, Tim Song <t.canens.cpp@gmail.com> wrote:
>
> https://clang.llvm.org/docs/LanguageExtensions.html#checks-for-type-trait-primitives
> seems to suggest using __has_extension instead.
Hmm, that doesn't work. Oh well.
next prev parent reply other threads:[~2017-07-31 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 7:27 Katsuhiko Nishimra
2017-07-31 14:53 ` Jonathan Wakely
2017-07-31 15:14 ` Tim Song
2017-07-31 17:23 ` Tim Song [this message]
2017-08-01 15:06 ` Katsuhiko Nishimra
2017-08-09 23:17 ` Jonathan Wakely
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='CAPQZVxtfgh71eQcRLJHeqt3BEDu++PNmz5+e=PWbL9fmAOO5xg@mail.gmail.com' \
--to=t.canens.cpp@gmail.com \
--cc=cfe-dev@lists.llvm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=ktns.87@gmail.com \
--cc=libstdc++@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).