public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wddawson at ucdavis dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/97084] New: Openmp + Allocatable String Crashes Date: Thu, 17 Sep 2020 10:28:05 +0000 [thread overview] Message-ID: <bug-97084-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97084 Bug ID: 97084 Summary: Openmp + Allocatable String Crashes Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: wddawson at ucdavis dot edu Target Milestone: --- Minimal example ``` program test implicit none integer :: ii integer, parameter :: N = 80 character(len=:), allocatable :: temp_string allocate(character(len=N) :: temp_string) !$omp parallel default(shared) !$omp do do ii = 1, N temp_string(ii:ii) = "#" end do !$omp end do !$omp end parallel end program ``` When I compile with `gfortran main.f90 -fopenmp -o test ` I get the following error: ``` during GIMPLE pass: omplower main.f90:9:0: 9 | !$omp parallel default(shared) | internal compiler error: in gimplify_expr, at gimplify.c:13885 libbacktrace could not find executable to open ``` It fails with the following compilers: ``` GNU Fortran (Homebrew GCC 10.2.0) 10.2.0 ``` ``` GNU Fortran (Homebrew GCC 9.3.0) 9.3.0 ``` But works with: ``` GNU Fortran (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39) ``` This is possibly related to 89621?
next reply other threads:[~2020-09-17 10:28 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-17 10:28 wddawson at ucdavis dot edu [this message] 2020-10-06 13:16 ` [Bug fortran/97084] " dominiq at lps dot ens.fr 2020-10-07 7:16 ` burnus at gcc dot gnu.org 2020-10-07 7:42 ` 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-97084-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).