public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "h2+bugs at fsfe dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106320] New: [10 regression] build failure (due to view requirement changes?) Date: Fri, 15 Jul 2022 21:03:39 +0000 [thread overview] Message-ID: <bug-106320-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106320 Bug ID: 106320 Summary: [10 regression] build failure (due to view requirement changes?) Product: gcc Version: 10.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: h2+bugs at fsfe dot org Target Milestone: --- The following snippet builds on GCC10.3, GCC11.3, GCC12.1 and even MSVC 19.32. It no longer builds on GCC10.4. This might be related to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103904 #include <ranges> #include <vector> int main() { auto l = std::views::transform([](auto v) { auto x = int{}; //!BROKEN - remove this capture and it will work return v | std::views::transform([x](auto v2) { return v2; }); }); std::vector<std::vector<int>> v{{5, 6, 7}}; v | l | std::views::join; }
next reply other threads:[~2022-07-15 21:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-15 21:03 h2+bugs at fsfe dot org [this message] 2022-07-18 7:40 ` [Bug libstdc++/106320] " rguenth at gcc dot gnu.org 2022-07-18 9:02 ` redi at gcc dot gnu.org 2022-07-18 9:30 ` marxin at gcc dot gnu.org 2022-07-18 10:35 ` redi at gcc dot gnu.org 2022-07-18 13:25 ` ppalka at gcc dot gnu.org 2022-07-22 16:53 ` cvs-commit at gcc dot gnu.org 2022-07-22 17:06 ` cvs-commit at gcc dot gnu.org 2022-07-22 17:49 ` h2+bugs at fsfe dot org 2022-09-12 19:05 ` cvs-commit at gcc dot gnu.org 2022-09-12 19:21 ` cvs-commit at gcc dot gnu.org 2022-09-12 19:23 ` ppalka 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-106320-4@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: linkBe 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).