From: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>
To: FX Coudert <fxcoudert@gmail.com>
Cc: "fortran@gcc.gnu.org List" <fortran@gcc.gnu.org>, gcc@gcc.gnu.org
Subject: Re: Call to arms: testsuite failures on various targets
Date: Wed, 18 Apr 2007 05:28:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.58.0704180011220.7417@caipclassic.rutgers.edu> (raw)
In-Reply-To: <490CA758-A04D-4FB3-A3E2-642F84A75902@gmail.com>
On Thu, 12 Apr 2007, FX Coudert wrote:
> Hi all,
>
> I reviewed this afternoon the postings from the gcc-testresults
> mailing-list for the past month, and we have a couple of gfortran
> testsuite failures showing up on various targets. Could people with
> access to said targets (possibly maintainers) please file PRs in
> bugzilla for each testcase, reporting the error message and/or
> backtrace? (I'd be happy to be added to the Cc list of these)
>
> [...]
> * sparc{,64}-sun-solaris2.10: gfortran.dg/open_errors.f90 gfortran.dg/
> vect/vect-5.f90 (and gfortran.dg/cray_pointers_2.f90 when using -fPIC)
The cray_pointers_2.f90 failure is already noted under PR30774, it's a
solaris issue not necessarily specific to fortran.
The other two, I've opened PRs 31615 and 31616.
--Kaveh
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu
next prev parent reply other threads:[~2007-04-18 4:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 21:35 FX Coudert
2007-04-12 21:50 ` FX Coudert
2007-04-13 0:31 ` Brooks Moses
2007-04-13 9:38 ` Jerry DeLisle
2007-04-13 12:31 ` Dave Korn
2007-04-13 19:04 ` Brooks Moses
2007-04-14 15:12 ` Tim Prince
2007-04-14 15:50 ` Dorit Nuzman
2007-04-14 18:17 ` Tim Prince
2007-04-14 18:50 ` Dorit Nuzman
2007-04-18 5:28 ` Kaveh R. GHAZI [this message]
2007-04-13 13:22 Dominique Dhumieres
2007-04-14 16:48 John David Anglin
[not found] <no.id>
2007-04-15 19:13 ` John David Anglin
[not found] <OF0D90E8B2.176B499E-ONC22572BD.00601B98-C22572BD.00649C26@LocalDomain>
2007-04-15 19:14 ` Dorit Nuzman
2007-04-16 3:19 ` Tim Prince
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=Pine.GSO.4.58.0704180011220.7417@caipclassic.rutgers.edu \
--to=ghazi@caip.rutgers.edu \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc@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).