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 testsuite/62250] FAIL: gfortran.dg/coarray/alloc_comp_1.f90 -fcoarray=lib -O2 -lcaf_single
Date: Wed, 07 Jan 2015 03:15:00 -0000 [thread overview]
Message-ID: <bug-62250-4-R0P6sCRb8T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62250-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62250
--- Comment #6 from dave.anglin at bell dot net ---
On 2015-01-06, at 9:06 PM, hp at gcc dot gnu.org wrote:
> But instead causing these tests to fail for all targets that don't have
> -latomic.
> I.e. -latomic should only be added when there is one, otherwise assume that
> support is built-in as before the patch. Also, the patch should have used
> atomic-dg.exp instead of manually adding the search paths.
That is clearly a better approach.
What about the gfortran.dg/coarray_lib_comm_1.f90 test? Do you see a better
alternative than adding "load_lib atomic-dg.exp" to gfortran.dg/dg.exp?
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2015-01-07 3:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-62250-4@http.gcc.gnu.org/bugzilla/>
2014-11-25 16:36 ` [Bug libfortran/62250] " danglin at gcc dot gnu.org
2015-01-04 1:23 ` [Bug testsuite/62250] " danglin at gcc dot gnu.org
2015-01-04 1:26 ` danglin at gcc dot gnu.org
2015-01-07 2:07 ` hp at gcc dot gnu.org
2015-01-07 3:10 ` hp at gcc dot gnu.org
2015-01-07 3:15 ` dave.anglin at bell dot net [this message]
2015-01-07 3:27 ` dave.anglin at bell dot net
2015-01-07 15:03 ` hp at gcc dot gnu.org
2015-01-07 15:38 ` dave.anglin at bell dot net
2015-01-08 21:58 ` hp at gcc dot gnu.org
2015-01-08 22:00 ` hp at gcc dot gnu.org
2015-01-09 19:22 ` dje at gcc dot gnu.org
2015-01-09 21:09 ` hp at bitrange dot com
2015-01-10 17:08 ` dje 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-62250-4-R0P6sCRb8T@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).