public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106837] False compilation error "inconsistent begin/end types in range-based 'for' statement" Date: Mon, 05 Sep 2022 13:35:59 +0000 [thread overview] Message-ID: <bug-106837-4-qmUtApXPx5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106837-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106837 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- True. But in the end the operator!= will be called on __begin and __end vars which are lvalues. So I think the test needs to be called on some trees with types of the *begin and *end return values for which lvalue_kind will say it is an lvalue. Dunno if that means trying to create a dummy VAR_DECL, CONST_DECL, PLACEHOLDER_EXPR, COMPOUND_LITERAL_EXPR or what else (and whether to do that only if *begin or *end aren't lvalues already.
next prev parent reply other threads:[~2022-09-05 13:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-05 13:17 [Bug c++/106837] New: " ofekshilon at gmail dot com 2022-09-05 13:22 ` [Bug c++/106837] " pinskia at gcc dot gnu.org 2022-09-05 13:30 ` ofekshilon at gmail dot com 2022-09-05 13:35 ` jakub at gcc dot gnu.org [this message] 2022-09-06 9:12 ` ofekshilon 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-106837-4-qmUtApXPx5@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).