public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/42484] ICE with -fopenmp Date: Sat, 26 Dec 2009 20:11:00 -0000 [thread overview] Message-ID: <20091226201118.4130.qmail@sourceware.org> (raw) In-Reply-To: <bug-42484-16146@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from janus at gcc dot gnu dot org 2009-12-26 20:11 ------- There is a pass 'diagnose_omp_blocks', which generates the error message for the C code. Its execution function is 'diagnose_omp_structured_block_errors' in omp-low.x, which is correctly called also for Fortran code. However, the checks in 'diagnose_sb_0' and 'diagnose_sb_2' don't seem to work for the Fortran test case. For the C code in comment #2, the GIMPLE_RETURN branch in diagnose_sb_2 is in effect and calls diagnose_sb_0, which throws the errror. For the Fortran case this does not work, since the RETURN is translated to a GOTO. However, GOTOs jumping out of an OMP CRITICAL section should also be rejected. (I still don't see where things go wrong.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42484
next prev parent reply other threads:[~2009-12-26 20:11 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-23 22:00 [Bug middle-end/42484] New: " janus at gcc dot gnu dot org 2009-12-24 13:54 ` [Bug middle-end/42484] " janus at gcc dot gnu dot org 2009-12-25 20:37 ` [Bug fortran/42484] " janus at gcc dot gnu dot org 2009-12-26 20:11 ` janus at gcc dot gnu dot org [this message] 2009-12-26 22:31 ` janus at gcc dot gnu dot org 2009-12-26 22:47 ` janus at gcc dot gnu dot org 2009-12-27 11:38 ` janus at gcc dot gnu dot org 2009-12-27 12:54 ` janus at gcc dot gnu dot org 2009-12-27 13:05 ` janus at gcc dot gnu dot org 2009-12-27 15:57 ` janus at gcc dot gnu dot org 2009-12-28 21:41 ` janus at gcc dot gnu dot 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=20091226201118.4130.qmail@sourceware.org \ --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).