public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "patrick.begou@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109622] internal compiler error: in omp_group_base, at gimplify.cc:9412 if -fopenacc is set. Date: Tue, 25 Apr 2023 10:32:26 +0000 [thread overview] Message-ID: <bug-109622-4-veWn5j7Ofd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109622-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109622 --- Comment #2 from Patrick Bégou <patrick.begou@univ-grenoble-alpes.fr> --- Sorry, exact branch is: releases/gcc-13
next prev parent reply other threads:[~2023-04-25 10:32 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-25 10:27 [Bug fortran/109622] New: " patrick.begou@univ-grenoble-alpes.fr 2023-04-25 10:29 ` [Bug fortran/109622] " patrick.begou@univ-grenoble-alpes.fr 2023-04-25 10:32 ` patrick.begou@univ-grenoble-alpes.fr [this message] 2023-04-25 12:25 ` patrick.begou@univ-grenoble-alpes.fr 2023-04-25 12:49 ` pault at gcc dot gnu.org 2023-04-25 12:51 ` [Bug fortran/109622] [13/14 regression] " pault at gcc dot gnu.org 2023-04-25 13:20 ` rguenth at gcc dot gnu.org 2023-04-25 13:59 ` [Bug fortran/109622] [13/14 regression][OpenACC] " burnus at gcc dot gnu.org 2023-04-25 16:38 ` patrick.begou@univ-grenoble-alpes.fr 2023-04-26 6:58 ` rguenth at gcc dot gnu.org 2023-04-28 11:03 ` burnus at gcc dot gnu.org 2023-04-28 11:34 ` cvs-commit at gcc dot gnu.org 2023-04-29 9:41 ` patrick.begou@univ-grenoble-alpes.fr 2023-05-04 11:52 ` cvs-commit at gcc dot gnu.org 2023-05-05 13:15 ` cvs-commit at gcc dot gnu.org 2023-05-05 13:15 ` cvs-commit at gcc dot gnu.org 2023-05-08 12:35 ` tschwinge at gcc dot gnu.org 2023-05-08 13:52 ` patrick.begou@univ-grenoble-alpes.fr 2023-05-08 13:56 ` burnus 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-109622-4-veWn5j7Ofd@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).