From: Joseph Myers <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
GNU C Library <libc-alpha@sourceware.org>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH v5 1/1] <sys/tagged-address.h>: An API for tagged address
Date: Thu, 5 Aug 2021 17:54:20 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2108051754050.137249@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAMe9rOoOnSCpp=HqA73-R2YWAGt-=NRiKMZB+Jkt++24pKNt+g@mail.gmail.com>
On Thu, 5 Aug 2021, H.J. Lu via Libc-alpha wrote:
> I can use _Static_assert directly for C. How should I use static_assert
> for C++?
Probably based on a test of the value of __cplusplus.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-08-05 17:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 13:13 [PATCH v5 0/1] RFC: Add <sys/tagged-address.h> H.J. Lu via Libc-alpha
2021-08-05 13:13 ` [PATCH v5 1/1] <sys/tagged-address.h>: An API for tagged address H.J. Lu via Libc-alpha
2021-08-05 17:26 ` Joseph Myers
2021-08-05 17:41 ` H.J. Lu via Libc-alpha
2021-08-05 17:54 ` Joseph Myers [this message]
2021-08-05 19:33 ` H.J. Lu via Libc-alpha
2021-08-12 8:36 ` Florian Weimer via Libc-alpha
2021-08-12 12:01 ` Szabolcs Nagy via Libc-alpha
2021-08-17 12:32 ` Szabolcs Nagy via Libc-alpha
2021-08-17 12:53 ` H.J. Lu via Libc-alpha
2021-08-17 14:59 ` Szabolcs Nagy via Libc-alpha
2021-08-17 15:37 ` H.J. Lu via Libc-alpha
2021-08-20 16:14 ` H.J. Lu via Libc-alpha
2021-08-20 16:25 ` Florian Weimer via Libc-alpha
2021-08-20 16:30 ` H.J. Lu via Libc-alpha
2021-08-20 23:26 ` H.J. Lu via Libc-alpha
2021-08-21 16:10 ` Sunil Pandey via Libc-alpha
2021-08-21 16:37 ` H.J. Lu via Libc-alpha
2021-08-21 21:20 ` Sunil Pandey via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2108051754050.137249@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.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).