From: Stephan Bergmann <sbergman@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org, Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: [PATCH] libstdc++: Make chrono::hh_mm_ss more compact
Date: Mon, 12 Dec 2022 17:30:33 +0100 [thread overview]
Message-ID: <088e7473-cfcc-b1b5-ad69-4e36a62e76b0@redhat.com> (raw)
In-Reply-To: <CAH6eHdQVtF0mPnx6NQnsmgiFdhu2EJ9ddJmS60yPZwtcURGGmQ@mail.gmail.com>
On 12/12/2022 12:18, Jonathan Wakely wrote:
> If Clang already treats __is_signed as a conditionally-active
> built-in, it should do the same for __is_unsigned.
Wasn't aware of that special handling of __is_signed. Filed
<https://reviews.llvm.org/D139847> "Also allow __is_unsigned to be used
as an identifier" now (just in case, even if the use in libstdc++ is
already gone again).
prev parent reply other threads:[~2022-12-12 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 20:43 Jonathan Wakely
2022-12-06 21:40 ` Jonathan Wakely
2022-12-12 7:10 ` Stephan Bergmann
2022-12-12 11:18 ` Jonathan Wakely
2022-12-12 14:06 ` Jonathan Wakely
2022-12-12 16:30 ` Stephan Bergmann [this message]
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=088e7473-cfcc-b1b5-ad69-4e36a62e76b0@redhat.com \
--to=sbergman@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@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).