public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45319] [4.5 Regression] FAIL: libgomp.fortran/vla4.f90 Date: Wed, 18 Aug 2010 14:32:00 -0000 [thread overview] Message-ID: <20100818143214.1062.qmail@sourceware.org> (raw) In-Reply-To: <bug-45319-276@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from danglin at gcc dot gnu dot org 2010-08-18 14:32 ------- Similar fails: FAIL: gfortran.dg/gomp/appendix-a/a.35.4.f90 -O (test for warnings, line 11) FAIL: gfortran.dg/gomp/appendix-a/a.35.4.f90 -O (test for excess errors) Excess errors: /mnt/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/gomp/appendix-a/a.35.4.f90:9:0: warni ng: barrier region may not be closely nested inside of work-sharing, critical, o rdered, master or explicit task region FAIL: libgomp.fortran/vla5.f90 -O0 (test for warnings, line 69) FAIL: libgomp.fortran/vla5.f90 -O0 (test for excess errors) Excess errors: /mnt/gnu/gcc/gcc/libgomp/testsuite/libgomp.fortran/vla5.f90:68:0: warning: barri er region may not be closely nested inside of work-sharing, critical, ordered, m aster or explicit task region -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45319
next prev parent reply other threads:[~2010-08-18 14:32 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-18 14:19 [Bug preprocessor/45319] New: " danglin at gcc dot gnu dot org 2010-08-18 14:32 ` danglin at gcc dot gnu dot org [this message] 2010-08-30 15:46 ` [Bug fortran/45319] [4.5 Regression] " rguenth at gcc dot gnu dot org 2010-09-21 9:28 ` burnus at gcc dot gnu dot org [not found] <bug-45319-4@http.gcc.gnu.org/bugzilla/> 2010-10-21 12:57 ` burnus at gcc dot gnu.org 2010-10-21 15:53 ` danglin 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=20100818143214.1062.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).