public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "sean yang" <seanatpurdue@hotmail.com>
To: gcc-help@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: LOTS of failures when making check for gfortran--is it  Ok?
Date: Fri, 23 Jun 2006 09:10:00 -0000	[thread overview]
Message-ID: <BAY105-F29BF92B318B43719723BEAC07A0@phx.gbl> (raw)

I successfully compile a GCC4.0.2 with Fortran front end. I tried to use it 
to compile some fortran programs, so far all of them work fine.

But the make check gave lots of failure. Is it tolerable to have thousands 
of failure?

objgcc-4.0.2>make -k check 1>record.tmp
objgcc-4.0.2>cat record.tmp

    71         === gcc Summary ===
     72
     73 # of expected passes        35255
     74 # of unexpected successes   1
     75 # of expected failures      94
     76 # of untested testcases     28
     77 # of unsupported tests      328

  4579         === gfortran Summary ===
   4580
   4581 # of expected passes        46
   4582 # of unexpected failures    4475
   4583 # of expected failures      1
   4584 # of unresolved testcases   2
   4585 # of untested testcases     1527
....
   4679
   4680         === libmudflap Summary ===
   4681
   4682 # of expected passes        1212
   4683 # of unexpected failures    48
....

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

             reply	other threads:[~2006-06-23  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23  9:10 sean yang [this message]
2006-06-23  9:14 ` Andrew Haley
2006-06-23 10:41 ` tobias.schlueter
2006-06-23 13:36   ` 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=BAY105-F29BF92B318B43719723BEAC07A0@phx.gbl \
    --to=seanatpurdue@hotmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-help@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).