public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: sotrdg sotrdg <euloanty@live.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: What about supporting std::numeric_limits, std::make_unsigned_t and std::integral concepts as an extension for __uint128_t and __int128_t??
Date: Sat, 23 May 2020 23:12:41 +0100	[thread overview]
Message-ID: <CAH6eHdShvAsBciOvKebN6JXXk+3Pv8aORjyVdTAFwZaYqQN8SA@mail.gmail.com> (raw)
In-Reply-To: <CH2PR02MB652214B53F50612D95AF2F19B2B50@CH2PR02MB6522.namprd02.prod.outlook.com>

On Sat, 23 May 2020 at 22:02, sotrdg sotrdg via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> It is absolutely a pain in a template world code like this do not work.
>
>                 std::make_unsigned_t<__int128_t>;
>                 static_assert(std::unsigned_integral<__uint128_t>);

They work with -std=gnu++NN options, but not with -std=c++NN options.

If you want to use non-standard extensions, us the gnu++ modes.

      parent reply	other threads:[~2020-05-23 22:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-23 20:56 sotrdg sotrdg
2020-05-23 21:26 ` Marc Glisse
2020-05-23 22:12 ` Jonathan Wakely [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=CAH6eHdShvAsBciOvKebN6JXXk+3Pv8aORjyVdTAFwZaYqQN8SA@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=euloanty@live.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).