public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/96042] Reference type of std::ranges::iota is __int128 with -std=c++2a?!
Date: Thu, 12 Nov 2020 14:34:57 +0000 [thread overview]
Message-ID: <bug-96042-4-fcquI41HOm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96042-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96042
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:a65261443a9b9cfac876c0b7e47393587eb1ce5c
commit r10-9015-ga65261443a9b9cfac876c0b7e47393587eb1ce5c
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Wed Aug 19 20:36:10 2020 +0100
libstdc++: Make make-unsigned-like-t<__int128> work [PR 96042]
As well as ensuring that numeric_limits<__int128> is defined, we need to
ensure that make-unsigned-like-t and to-unsigned-like work correctly for
128-bit integers in strict mode. This ensures that a subrange created
from an iota_view's iterator and sentinel can represent its size.
Co-authored-by: Patrick Palka <ppalka@redhat.com>
libstdc++-v3/ChangeLog:
2020-08-19 Jonathan Wakely <jwakely@redhat.com>
Patrick Palka <ppalka@redhat.com>
PR libstdc++/96042
* include/bits/range_access.h (__detail::__to_unsigned_like):
Do not use make_unsigned_t<T> in the return type, as it can
result in an error before the integral<T> constraint is checked.
[__STRICT_ANSI__]: Add overloads for 128-bit integer types.
(__detail::__make_unsigned_like_t): Define as the return type
of __to_unsigned_like.
* testsuite/std/ranges/subrange/96042.cc: New test.
(cherry picked from commit e6e01618e83bcd9eb3a2b27df30ed87106a748b4)
next prev parent reply other threads:[~2020-11-12 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 22:53 [Bug libstdc++/96042] New: " gcc-bugs at marehr dot dialup.fu-berlin.de
2020-07-03 11:03 ` [Bug libstdc++/96042] " redi at gcc dot gnu.org
2020-07-03 12:47 ` gcc-bugs at marehr dot dialup.fu-berlin.de
2020-07-06 11:35 ` redi at gcc dot gnu.org
2020-07-07 1:07 ` rs2740 at gmail dot com
2020-07-07 12:20 ` redi at gcc dot gnu.org
2020-08-19 15:38 ` redi at gcc dot gnu.org
2020-08-19 15:59 ` cvs-commit at gcc dot gnu.org
2020-08-19 19:36 ` cvs-commit at gcc dot gnu.org
2020-11-12 14:09 ` cvs-commit at gcc dot gnu.org
2020-11-12 14:34 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-12 14:35 ` redi at gcc dot gnu.org
2020-11-13 13:11 ` cvs-commit at gcc dot gnu.org
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=bug-96042-4-fcquI41HOm@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).