From: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de>
To: gcc@gcc.gnu.org
Cc: toon@moene.indiv.nluug.nl
Subject: Fortran and test suite on the 3.0 branch
Date: Sat, 09 Jun 2001 01:19:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0106091118140.28867-100000@snake.iap.physik.tu-darmstadt.de> (raw)
Since recent g77 compilers on 3.0 branch compile the file
g77.f-torture/compile/20000629-1.f without a problem on the
i686-pc-linux-gnu target, could you please remove the file
gcc/testsuite/g77.f-torture/compile/20000629-1.x, as you did for the
mainline some time ago.
Thank you,
Peter Schmid
=== g77 tests ===
Schedule of variations:
unix
Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic interface file for target.
Using /mnt/egcs/gcc/gcc/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /mnt/egcs/gcc/gcc/testsuite/g77.dg/dg.exp ...
Running /mnt/egcs/gcc/gcc/testsuite/g77.f-torture/compile/compile.exp ...
XPASS: g77.f-torture/compile/20000629-1.f, -O3 -fomit-frame-pointer -funroll-loops
XPASS: g77.f-torture/compile/20000629-1.f, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
Running /mnt/egcs/gcc/gcc/testsuite/g77.f-torture/execute/execute.exp ...
Running /mnt/egcs/gcc/gcc/testsuite/g77.f-torture/noncompile/noncompile.exp ...
=== g77 Summary ===
# of expected passes 947
# of unexpected successes 2
/mnt/egcs/build/gcc/g77 g77 version 3.0 20010608 (prerelease) (Fortran Frontend version 0.5.26 20010608 (experimental))
next reply other threads:[~2001-06-09 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 1:19 Peter Schmid [this message]
2001-06-09 12:18 ` Toon Moene
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.LNX.4.21.0106091118140.28867-100000@snake.iap.physik.tu-darmstadt.de \
--to=schmid@snake.iap.physik.tu-darmstadt.de \
--cc=gcc@gcc.gnu.org \
--cc=toon@moene.indiv.nluug.nl \
/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).