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 fortran/110725] [13/14 Regression] internal compiler error: in expand_expr_real_1, at expr.cc:10897 Date: Mon, 24 Jul 2023 15:04:59 +0000 [thread overview] Message-ID: <bug-110725-4-KhgtNhGqGk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110725-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110725 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org, | |jakub at gcc dot gnu.org --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- This is certainly accepts-invalid if it is accepted. E.g. OpenMP 5.0 says on this in 2.20, 5.1 in https://www.openmp.org/spec-html/5.1/openmpse30.html#x155-1880002.22 "If a teams construct is nested within a target construct, that target construct must contain no statements, declarations or directives outside of the teams construct." Though, diagnosing this is hard, because e.g. parsing of teams construct's clauses can result in some code in between the target and teams nested in it, and that is valid. I mean say int foo (void) { return 42; } #pragma omp declare target (foo) int main () { #pragma omp target #pragma omp teams num_teams (foo ()) ; }
next prev parent reply other threads:[~2023-07-24 15:05 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-18 17:22 [Bug fortran/110725] New: " tonycurtis32 at gmail dot com 2023-07-18 17:56 ` [Bug fortran/110725] [13/14 Regression] " anlauf at gcc dot gnu.org 2023-07-18 18:55 ` [Bug fortran/110725] [13/14 Regression,openmp] " kargl at gcc dot gnu.org 2023-07-19 6:47 ` [Bug fortran/110725] [13/14 Regression] " rguenth at gcc dot gnu.org 2023-07-19 17:44 ` kargl at gcc dot gnu.org 2023-07-24 15:04 ` jakub at gcc dot gnu.org [this message] 2023-07-24 20:58 ` cvs-commit at gcc dot gnu.org 2023-07-25 13:45 ` cvs-commit at gcc dot gnu.org 2023-07-27 9:27 ` rguenth at gcc dot gnu.org 2023-07-27 16:17 ` cvs-commit at gcc dot gnu.org 2024-03-04 4:54 ` law 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-110725-4-KhgtNhGqGk@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).