public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Tue, 25 Jul 2023 13:45:03 +0000 [thread overview] Message-ID: <bug-110725-4-R4TugoDniS@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 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>: https://gcc.gnu.org/g:09dda270380fe13e7b4722305cb1122df1f779a0 commit r14-2761-g09dda270380fe13e7b4722305cb1122df1f779a0 Author: Tobias Burnus <tobias@codesourcery.com> Date: Tue Jul 25 15:43:58 2023 +0200 OpenMP/Fortran: Reject declarations between target + teams While commit r14-2754-g2e31fe431b08b0302e1fa8a1c18ee51adafd41df detected executable statements, declarations do not show up as executable statements. Hence, we now check whether the first statement after TARGET is TEAMS - such that we can detect data statements like type or variable declarations. Fortran semantics ensures that only executable directives/statemens can come after '!$omp end teams' such that those can be detected with the previous check. Note that statements returning ST_NONE such as 'omp nothing' or 'omp error at(compilation)' will still slip through. PR fortran/110725 PR middle-end/71065 gcc/fortran/ChangeLog: * gfortran.h (gfc_omp_clauses): Add target_first_st_is_teams. * parse.cc (parse_omp_structured_block): Set it if the first statement in the structured block of a TARGET is TEAMS or a combined/composite starting with TEAMS. * openmp.cc (resolve_omp_target): Also show an error for contains_teams_construct without target_first_st_is_teams. gcc/testsuite/ChangeLog: * gfortran.dg/gomp/teams-6.f90: New test.
next prev parent reply other threads:[~2023-07-25 13:45 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 2023-07-24 20:58 ` cvs-commit at gcc dot gnu.org 2023-07-25 13:45 ` cvs-commit at gcc dot gnu.org [this message] 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-R4TugoDniS@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).