From: David Daney <ddaney@avtrex.com>
To: GCC Mailing List <gcc@gcc.gnu.org>, fortran@gcc.gnu.org
Cc: Richard Sandiford <rsandifo@nildram.co.uk>
Subject: MIPS/FORTRAN failures...
Date: Sat, 05 Jan 2008 20:38:00 -0000 [thread overview]
Message-ID: <477FEA9D.1090306@avtrex.com> (raw)
The gfortran.dg/optional_dim_2.f90 test has been failing on mipsel-linux
ever since it was added.
See:
http://gcc.gnu.org/ml/gcc-testresults/2008-01/msg00204.html
http://gcc.gnu.org/ml/gcc-testresults/2007-11/msg01522.html
http://gcc.gnu.org/ml/gcc-testresults/2007-11/msg01430.html
I don't really have time to look at it for the next few weeks. But if
another mips or fortran hacker were to fix it, we would have clean
testsuite results for fortran on mips.
David Daney
next reply other threads:[~2008-01-05 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 20:38 David Daney [this message]
2008-01-06 8:57 ` Tobias Burnus
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=477FEA9D.1090306@avtrex.com \
--to=ddaney@avtrex.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=rsandifo@nildram.co.uk \
/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).