public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/100661] [11/12 Regression] ICE in omp-low.c / refs_may_alias_p_2, at tree-ssa-alias.c:2460
Date: Thu, 20 Jan 2022 13:41:29 +0000	[thread overview]
Message-ID: <bug-100661-4-yZT3z6Ek1c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100661-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100661

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Can lambdas appear inside #pragma omp in C++?  The following is accepted but
each thread seems to get the global 'c', but at least we don't ICE (possibly
because frame lowering is done in the FE).

void
foo (char **x)
{
  #pragma omp parallel for
  for (int i = 0; i < 16; i++)
    {
      char c[50];
      __builtin_strcpy (c, x[i]);
      auto x = [&] () { __builtin_strcat (c, "foo"); };
      x();
    }
}

  parent reply	other threads:[~2022-01-20 13:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 17:48 [Bug c/100661] New: [11/12 Regression] ICE in " gscfq@t-online.de
2021-05-19  8:01 ` [Bug c/100661] [11/12 Regression] ICE in omp-low.c / " rguenth at gcc dot gnu.org
2021-05-19 12:15 ` marxin at gcc dot gnu.org
2021-05-20 16:33 ` jakub at gcc dot gnu.org
2021-07-28  7:07 ` rguenth at gcc dot gnu.org
2022-01-20 13:41 ` rguenth at gcc dot gnu.org [this message]
2022-01-20 13:43 ` rguenth at gcc dot gnu.org
2022-01-20 13:48 ` jakub at gcc dot gnu.org
2022-03-23  8:36 ` [Bug c/100661] ICE in omp-low.c / refs_may_alias_p_2, at tree-ssa-alias.c:2460 with nested function in OMP region rguenth at gcc dot gnu.org
2024-04-02  5:47 ` 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-100661-4-yZT3z6Ek1c@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).