public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91780] Discrepancy between gcc 7.4, through 9.2, compared to clang.
Date: Fri, 17 Dec 2021 10:38:54 +0000 [thread overview]
Message-ID: <bug-91780-4-HGxLIuDxad@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91780-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91780
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Before that commit, the zip(as, bs) deduced the type as zip<vector<int>,
vector<int>>, rather than zip<vector<int>&, vector<int>&>.
So:
(In reply to Mikael Persson from comment #0)
> GCC does not change values in tuple of references
Is wrong. There isn't a tuple of references there at all, that's why the
changes were not visible in the original obejcts. The zip created its own
copies, and then those were modified.
next prev parent reply other threads:[~2021-12-17 10:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91780-4@http.gcc.gnu.org/bugzilla/>
2021-12-17 4:53 ` pinskia at gcc dot gnu.org
2021-12-17 10:21 ` redi at gcc dot gnu.org
2021-12-17 10:25 ` pinskia at gcc dot gnu.org
2021-12-17 10:26 ` pinskia at gcc dot gnu.org
2021-12-17 10:38 ` redi at gcc dot gnu.org [this message]
2021-12-17 10:46 ` redi at gcc dot gnu.org
2021-12-17 10:51 ` redi at gcc dot gnu.org
2021-12-19 7:54 ` mikael.p.persson at gmail dot com
2021-12-19 13:00 ` redi at gcc dot gnu.org
2021-12-19 15:03 ` mikael.p.persson at gmail dot com
2021-12-20 7:05 ` mikael.p.persson at gmail dot com
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-91780-4-HGxLIuDxad@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).