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: Fri, 13 Nov 2020 13:11:12 +0000 [thread overview]
Message-ID: <bug-96042-4-KspFhRI6iQ@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 #11 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:12042aeb9336f20b9225b2e5139e5f6c9bde7642
commit r10-9021-g12042aeb9336f20b9225b2e5139e5f6c9bde7642
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Fri Nov 13 13:04:10 2020 +0000
libstdc++: Fix test that fails for targets without __int128 [PR 96042]
When backporting this test (and the changes it depends on) I forgot that
the __max_diff_type and __max_size_type classes are only present on
trunk, not the gcc-10 branch. That using iota_view<long long, long long>
oonly works correctly when __int128 is available, so the test fails on
32-bit targets.
This just skips the failing check.
PR libstdc++/96042
* testsuite/std/ranges/iota/96042.cc: Only assert that the
difference type is wider than long long if __int128 is
supported.
prev parent reply other threads:[~2020-11-13 13:11 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
2020-11-12 14:35 ` redi at gcc dot gnu.org
2020-11-13 13:11 ` cvs-commit at gcc dot gnu.org [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=bug-96042-4-KspFhRI6iQ@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).