public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/23554] New: FAIL: gfortran.dg/namelist_14.f90
Date: Wed, 24 Aug 2005 23:11:00 -0000 [thread overview]
Message-ID: <20050824230752.23554.danglin@gcc.gnu.org> (raw)
Executing on host: /test/gnu/gcc-3.3/objdir/gcc/testsuite/../gfortran -B/test/gn
u/gcc-3.3/objdir/gcc/testsuite/../ /test/gnu/gcc-3.3/gcc/gcc/testsuite/gfortran.
dg/namelist_14.f90 -O0 -pedantic-errors -L/test/gnu/gcc-3.3/objdir/hppa2.0w
-hp-hpux11.11/./libgfortran/.libs -L/test/gnu/gcc-3.3/objdir/hppa2.0w-hp-hpux11.
11/./libiberty -lm -o ./namelist_14.exe (timeout = 300)
PASS: gfortran.dg/namelist_14.f90 -O0 (test for excess errors)
Setting LD_LIBRARY_PATH to .:/test/gnu/gcc-3.3/objdir/hppa2.0w-hp-hpux11.11/./li
bgfortran/.libs:/test/gnu/gcc-3.3/objdir/gcc:.:/test/gnu/gcc-3.3/objdir/hppa2.0w
-hp-hpux11.11/./libgfortran/.libs:/test/gnu/gcc-3.3/objdir/gcc
FAIL: gfortran.dg/namelist_14.f90 -O0 execution test
--
Summary: FAIL: gfortran.dg/namelist_14.f90
Product: gcc
Version: 4.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: danglin at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: hppa2.0w-hp-hpux11.11
GCC host triplet: hppa2.0w-hp-hpux11.11
GCC target triplet: hppa2.0w-hp-hpux11.11
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23554
next reply other threads:[~2005-08-24 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 23:11 danglin at gcc dot gnu dot org [this message]
2005-08-24 23:14 ` [Bug target/23554] " pinskia at gcc dot gnu dot org
2005-09-02 21:55 ` sje at cup dot hp dot com
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=20050824230752.23554.danglin@gcc.gnu.org \
--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).