public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: JeanHeyd Meneide <phdofthehouse@gmail.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] libstdc++: Make __int128 meet integer-class requirements [PR 96042]
Date: Sat, 22 Aug 2020 13:32:08 +0100	[thread overview]
Message-ID: <CAH6eHdS73K2kh0MH4uiE9YLhXK55PVUwTe4MKWDUHomO-kUZug@mail.gmail.com> (raw)
In-Reply-To: <CANHA4Og-aY1hZDdsGNZRkbjXKDpLrgBzKMHnDzemiFF3T2D26A@mail.gmail.com>

On Sat, 22 Aug 2020 at 13:18, JeanHeyd Meneide wrote:
>
> On Sat, Aug 22, 2020 at 8:14 AM Jonathan Wakely via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
> > I really wish WG14 would just fix the intmax_t mess so we can make
> > them integral types unconditionally.
>
> We're trying, but we're struggling to reach a good consensus. Almost
> nobody's fully agreeing on one /particular/ solution (there's roughly
> 3 ideas of what to do).

I liked Jens Gustedt's original proposal, it looked perfect to me. I
should catch up on WG14 mails to see what the other proposals are and
where the discussion is going.

  reply	other threads:[~2020-08-22 12:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 16:00 Jonathan Wakely
2020-08-19 19:36 ` Jonathan Wakely
2020-08-20 18:44   ` Jonathan Wakely
2020-08-22  9:50 ` Marc Glisse
2020-08-22 12:13   ` Jonathan Wakely
2020-08-22 12:17     ` JeanHeyd Meneide
2020-08-22 12:32       ` Jonathan Wakely [this message]
2020-08-22 12:37     ` Jonathan Wakely
2020-08-22 15:00       ` Marc Glisse
2020-08-24  8:52         ` 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=CAH6eHdS73K2kh0MH4uiE9YLhXK55PVUwTe4MKWDUHomO-kUZug@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=phdofthehouse@gmail.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).