public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "abensonca at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/66633] New: ICE on valid "verify_gimple failed" with OpenMP Date: Tue, 23 Jun 2015 01:23:00 -0000 [thread overview] Message-ID: <bug-66633-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66633 Bug ID: 66633 Summary: ICE on valid "verify_gimple failed" with OpenMP Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: abensonca at gmail dot com Target Milestone: --- The following causes an ICE in gfortran 6.0.0 (r224761): module spls type :: spc contains procedure :: l => spcL end type spc contains function spl() class(spc), pointer :: spc_ !$omp parallel write (0,*) igrt(fli) !$omp end parallel contains double precision function fli() fli=spc_%l() end function fli end function spl double precision function spcL(s) implicit none class(spc), intent(inout) :: s return end function spcL end module spls $ gfortran -v Using built-in specs. COLLECT_GCC=/opt/gcc-trunk/bin/gfortran COLLECT_LTO_WRAPPER=/opt/gcc-trunk/libexec/gcc/x86_64-unknown-linux-gnu/6.0.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../gcc-trunk/configure --prefix=/opt/gcc-trunk --enable-languages=c,c++,fortran --disable-multilib Thread model: posix gcc version 6.0.0 20150622 (experimental) (GCC) gfortran -c tmp.F90 -o tmp.o -fopenmp tmp.F90:11:0: write (0,*) igrt(fli) ^ Error: invalid argument to gimple call &<<< error >>>.fli D.3429 = __builtin_adjust_trampoline (&<<< error >>>.fli); tmp.F90:11:0: internal compiler error: verify_gimple failed 0xbaf19d verify_gimple_in_seq(gimple_statement_base*) ../../gcc-trunk/gcc/tree-cfg.c:4790 0xab14b0 execute_function_todo ../../gcc-trunk/gcc/passes.c:1987 0xab1c63 execute_todo ../../gcc-trunk/gcc/passes.c:2042 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2015-06-23 1:23 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-23 1:23 abensonca at gmail dot com [this message] 2015-06-23 3:26 ` [Bug fortran/66633] " abensonca at gmail dot com 2015-06-23 9:44 ` mikael at gcc dot gnu.org 2015-06-24 9:30 ` [Bug fortran/66633] [5/6 regression] " mikael at gcc dot gnu.org 2015-06-24 9:50 ` dominiq at lps dot ens.fr 2015-06-25 9:43 ` mikael at gcc dot gnu.org 2015-06-25 14:56 ` ebotcazou at gcc dot gnu.org 2015-06-26 9:12 ` ebotcazou at gcc dot gnu.org 2015-06-26 9:16 ` ebotcazou at gcc dot gnu.org 2015-06-26 9:27 ` [Bug middle-end/66633] " ebotcazou at gcc dot gnu.org 2015-07-01 8:22 ` ebotcazou at gcc dot gnu.org 2015-07-01 8:26 ` ebotcazou at gcc dot gnu.org 2015-07-01 19:20 ` abensonca at gmail dot com 2015-07-01 20:49 ` ebotcazou at gcc dot gnu.org 2015-07-09 17:46 ` jakub at gcc dot gnu.org 2015-07-09 21:14 ` jakub at gcc dot gnu.org 2015-07-10 14:13 ` jakub at gcc dot gnu.org 2015-07-10 14:14 ` jakub 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-66633-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).