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 middle-end/114509] [11/12/13/14 Regression] an infinite loop or ICE with openmp after errors in some cases Date: Wed, 17 Apr 2024 14:42:49 +0000 [thread overview] Message-ID: <bug-114509-4-7uS6EwA3Hd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114509-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114509 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Reduced testcase: void bar (void *); void foo (int x) { struct S { int a[x]; int b; } s; #pragma omp parallel for for (int i = 0; i < 10; i++) bar (&s); } We don't really support variable length structures/unions in OpenMP/OpenACC lowering/expansion, and I don't see why we should spend time on that, variable length structures/unions just shouldn't be used in C (they are already invalid in C++ and not present in Fortran either), I think that extension exists just because Ada needs to support that. Though Ada on the other side doesn't support OpenMP/OpenACC. So, I think we should just sorry if something attempts to privatize/map variable length structure/union; making it shared should be fine.
prev parent reply other threads:[~2024-04-17 14:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-28 6:39 [Bug c/114509] New: Infinite loop with openmp gccbugs at dima dot secretsauce.net 2024-03-28 7:03 ` [Bug middle-end/114509] [11/12/13/14 Regression] an infinite loop with openmp after errors in some cases pinskia at gcc dot gnu.org 2024-03-29 23:48 ` [Bug middle-end/114509] [11/12/13/14 Regression] an infinite loop or ICE " law at gcc dot gnu.org 2024-04-02 8:01 ` rguenth at gcc dot gnu.org 2024-04-17 14:42 ` jakub at gcc dot gnu.org [this message]
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-114509-4-7uS6EwA3Hd@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).