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 middle-end/113724] [14 Regression][OpenMP] ICE (segfault) when mapping a struct in omp_gather_mapping_groups_1 Date: Tue, 26 Mar 2024 10:58:02 +0000 [thread overview] Message-ID: <bug-113724-4-fOOCMBrGcZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113724-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113724 --- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- With release checking we ICE with t.c: In function 'main': t.c:46:11: internal compiler error: Segmentation fault 46 | #pragma omp target data map(S1.p[:N],S1.p,S1.a,S1.b) | ^~~ 0xd320af crash_signal /home/rguenther/src/trunk/gcc/toplev.cc:319 0xa3b5b0 omp_gather_mapping_groups_1 /home/rguenther/src/trunk/gcc/gimplify.cc:9593 0xa3b769 omp_gather_mapping_groups /home/rguenther/src/trunk/gcc/gimplify.cc:9621
next prev parent reply other threads:[~2024-03-26 10:58 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-02 15:39 [Bug middle-end/113724] New: " burnus at gcc dot gnu.org 2024-02-05 8:51 ` [Bug middle-end/113724] " rguenth at gcc dot gnu.org 2024-02-06 12:04 ` burnus at gcc dot gnu.org 2024-02-07 18:21 ` burnus at gcc dot gnu.org 2024-02-07 18:51 ` burnus at gcc dot gnu.org 2024-02-10 11:51 ` burnus at gcc dot gnu.org 2024-02-10 18:08 ` burnus at gcc dot gnu.org 2024-02-13 10:40 ` burnus at gcc dot gnu.org 2024-03-07 20:42 ` law at gcc dot gnu.org 2024-03-26 10:52 ` rguenth at gcc dot gnu.org 2024-03-26 10:58 ` rguenth at gcc dot gnu.org [this message] 2024-04-18 15:23 ` [Bug middle-end/113724] [14 Regression][OpenMP] ICE (segfault) when mapping a struct in omp_gather_mapping_groups_1 since r14-6515 jakub at gcc dot gnu.org 2024-04-26 8:41 ` jakub at gcc dot gnu.org 2024-05-07 7:44 ` [Bug middle-end/113724] [14/15 " rguenth 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-113724-4-fOOCMBrGcZ@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).