public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/55884] [4.8 Regression] FAIL: libgomp.fortran/omp_parse3.f90 -O0 (test for excess errors)
Date: Tue, 08 Jan 2013 03:34:00 -0000 [thread overview]
Message-ID: <bug-55884-4-LRv2kGB3gm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55884-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55884
--- Comment #5 from dave.anglin at bell dot net 2013-01-08 03:34:15 UTC ---
With the patch, the tests are unresolved with r194997:
UNSUPPORTED: libgomp.fortran/omp_parse3.f90 -O0
UNSUPPORTED: libgomp.fortran/omp_parse3.f90 -O1
UNSUPPORTED: libgomp.fortran/omp_parse3.f90 -O2
UNSUPPORTED: libgomp.fortran/omp_parse3.f90 -O3 -fomit-frame-pointer
UNSUPPORTED: libgomp.fortran/omp_parse3.f90 -O3 -fomit-frame-pointer -
funroll-loops
UNSUPPORTED: libgomp.fortran/omp_parse3.f90 -O3 -fomit-frame-pointer -
funroll-all-loops -finline-functions
UNSUPPORTED: libgomp.fortran/omp_parse3.f90 -O3 -g
UNSUPPORTED: libgomp.fortran/omp_parse3.f90 -Os
I'm fairly certain that the tests passed before the -fintrinsic-
modules-path was added to fortran.exp.
On 7-Jan-13, at 7:50 AM, jakub at gcc dot gnu.org wrote:
> Can you try perhaps:
> --- libgomp/testsuite/libgomp.fortran/fortran.exp 2012-12-20
> 11:38:48.663282599 +0100
> +++ libgomp/testsuite/libgomp.fortran/fortran.exp 2013-01-07
> 13:45:51.557361907 +0100
> @@ -14,7 +14,7 @@ set quadmath_library_path "../libquadmat
> dg-init
>
> if { $blddir != "" } {
> - lappend ALWAYS_CFLAGS "additional_flags=-fintrinsic-modules-path
> ${blddir}"
> + lappend ALWAYS_CFLAGS "additional_flags=-fintrinsic-modules-path
> ${blddir}"
> # Look for a static libgfortran first.
> if [file exists "${blddir}/${lang_library_path}/libgfortran.a"] {
> set lang_test_file "${lang_library_path}/libgfortran.a"
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2013-01-08 3:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 16:30 [Bug driver/55884] New: " danglin at gcc dot gnu.org
2013-01-05 16:37 ` [Bug driver/55884] [4.8 Regression] " danglin at gcc dot gnu.org
2013-01-05 18:59 ` danglin at gcc dot gnu.org
2013-01-07 10:06 ` rguenth at gcc dot gnu.org
2013-01-07 12:51 ` jakub at gcc dot gnu.org
2013-01-07 16:09 ` dave.anglin at bell dot net
2013-01-08 3:34 ` dave.anglin at bell dot net [this message]
2013-01-08 8:13 ` jakub at gcc dot gnu.org
2013-01-08 15:30 ` dave.anglin at bell dot net
2013-01-09 4:16 ` dave.anglin at bell dot net
2013-01-09 4:46 ` dave.anglin at bell dot net
2013-01-13 21:27 ` dave.anglin at bell dot net
2013-01-16 16:20 ` burnus at gcc dot gnu.org
2013-01-16 16:36 ` 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-55884-4-LRv2kGB3gm@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: link
Be 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).