public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108317] dependent vector field is not causing this to be captured for fold expression inside a if constexpr block Date: Fri, 06 Jan 2023 18:04:18 +0000 [thread overview] Message-ID: <bug-108317-4-IvRlw1ma4s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108317-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108317 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|#1 SMP PREEMPT_DYNAMIC Sat, | |31 Dec 2022 17:40:35 +0000 | Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2023-01-06 Summary|g++ is unable to capture |dependent vector field is |vector-extended variables |not causing this to be | |captured for fold | |expression inside a if | |constexpr block Host|#1 SMP PREEMPT_DYNAMIC Sat, | |31 Dec 2022 17:40:35 +0000 | --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced testcase: template <typename T> struct pint { T __attribute__ ((vector_size (2 * sizeof(T)))) v_; void f(pint const& o) { [&]<int ...I>() { ( [&]() noexcept { if constexpr(I) { v_[I]; } }(), ... ); }.template operator()<0, 1>(); } }; int main() { using D = pint<int>; D a; D b; a.f(b); return 0; }
next prev parent reply other threads:[~2023-01-06 18:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-06 14:11 [Bug c++/108317] New: g++ is unable to capture vector-extended variables janezz55 at gmail dot com 2023-01-06 14:11 ` [Bug c++/108317] " janezz55 at gmail dot com 2023-01-06 18:04 ` pinskia at gcc dot gnu.org [this message] 2023-01-06 18:07 ` [Bug c++/108317] dependent vector field is not causing field of this not to be found for fold expression inside a if constexpr block pinskia at gcc dot gnu.org 2023-01-06 18:10 ` pinskia 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-108317-4-IvRlw1ma4s@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).