public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "townsend at astro dot wisc.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/56655] Associate construct with OpenMP triggers ICE Date: Wed, 20 Mar 2013 13:25:00 -0000 [thread overview] Message-ID: <bug-56655-4-FJvFix2MdK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56655-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56655 --- Comment #2 from Rich Townsend <townsend at astro dot wisc.edu> 2013-03-20 13:25:15 UTC --- (In reply to comment #1) > (In reply to comment #0) > > Created attachment 29692 [details] > > Test source file to reproduce the error > > > > Attempting to compile the attached file with > > > > gfortran -fopenmp -c openmp_ice.f90 > > The file in the attachment is called 'test_h5_attr.f90' and I don't find any > ASSOCIATE construct in there. Wrong file attached? (In reply to comment #1) > (In reply to comment #0) > > Created attachment 29692 [details] > > Test source file to reproduce the error > > > > Attempting to compile the attached file with > > > > gfortran -fopenmp -c openmp_ice.f90 > > The file in the attachment is called 'test_h5_attr.f90' and I don't find any > ASSOCIATE construct in there. Wrong file attached? Ooops -- wrong test case. Here it is: subroutine sub (x) implicit none real, intent(in) :: x !$omp single associate(x_a => x) end associate !$omp end single end subroutine sub
next prev parent reply other threads:[~2013-03-20 13:25 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-20 0:55 [Bug fortran/56655] New: " townsend at astro dot wisc.edu 2013-03-20 9:47 ` [Bug fortran/56655] " janus at gcc dot gnu.org 2013-03-20 13:25 ` townsend at astro dot wisc.edu [this message] 2013-03-20 14:28 ` [Bug fortran/56655] [F03] ASSOCIATE " janus at gcc dot gnu.org 2013-08-12 12:50 ` janus at gcc dot gnu.org 2014-01-07 10:01 ` dominiq at lps dot ens.fr 2014-05-02 10:29 ` dominiq at lps dot ens.fr
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-56655-4-FJvFix2MdK@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).