public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100777] New: MMA builtin usage ICEs when used in a #pragma omp parallel and using -fopenmp Date: Wed, 26 May 2021 18:26:16 +0000 [thread overview] Message-ID: <bug-100777-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100777 Bug ID: 100777 Summary: MMA builtin usage ICEs when used in a #pragma omp parallel and using -fopenmp Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: bergner at gcc dot gnu.org Target Milestone: --- bergner@pike:~/$ cat bug.i void foo (__vector_quad *dst) { #pragma omp parallel { __builtin_mma_xxsetaccz (dst); } } bergner@pike:~/$ gcc -S -O1 -mcpu=power10 -fopenmp bug.i during GIMPLE pass: ssa bug.i: In function ‘foo’: bug.i:8:1: internal compiler error: Segmentation fault 8 | } | ^ 0x10b89f63 crash_signal /home/bergner/gcc/gcc-fsf-mainline-base/gcc/toplev.c:327 0x10ea5a00 verify_ssa(bool, bool) /home/bergner/gcc/gcc-fsf-mainline-base/gcc/tree-ssa.c:1070 ... This fails on trunk back to GCC10 (ie, first MMA support).
next reply other threads:[~2021-05-26 18:26 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-26 18:26 bergner at gcc dot gnu.org [this message] 2021-05-26 18:28 ` [Bug target/100777] " bergner at gcc dot gnu.org 2021-05-26 21:17 ` bergner at gcc dot gnu.org 2021-06-14 21:57 ` cvs-commit at gcc dot gnu.org 2021-06-14 22:06 ` bergner at gcc dot gnu.org 2021-06-17 22:04 ` cvs-commit at gcc dot gnu.org 2021-06-18 3:17 ` cvs-commit at gcc dot gnu.org 2021-06-18 20:24 ` bergner 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-100777-4@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).