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/33595] New: FAIL: gfortran.dg/nint_2.f90 -O0 execution test
Date: Sat, 29 Sep 2007 21:27:00 -0000 [thread overview]
Message-ID: <bug-33595-276@http.gcc.gnu.org/bugzilla/> (raw)
Executing on host: /test/gnu/gcc/objdir/gcc/testsuite/gfortran/../../gfortran
-B/test/gnu/gcc/objdir/gcc/testsuite/gfortran/../../
/test/gnu/gcc/gcc/gcc/testsuite/gfortran.dg/nint_2.f90 -O0 -pedantic-errors
-L/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran/.libs
-L/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran/.libs
-L/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libiberty -lm -o ./nint_2.exe
(timeout = 300)
PASS: gfortran.dg/nint_2.f90 -O0 (test for excess errors)
Setting LD_LIBRARY_PATH to
.:/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran/.libs:/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran/.libs:/test/gnu/gcc/objdir/gcc:.:/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran/.libs:/test/gnu/gcc/objdir/hppa64-hp-hpux11.11/./libgfortran/.libs:/test/gnu/gcc/objdir/gcc
FAIL: gfortran.dg/nint_2.f90 -O0 execution test
30 if (j1 /= 0 .or. j2 /= 0) call abort
(gdb)
Program received signal SIGABRT, Aborted.
0xc0000000001fa3dc in ?? ()
(gdb) p j1
$1 = 1
(gdb) p j2
$2 = 0
(gdb) p b
$3 = 0.49999997
--
Summary: FAIL: gfortran.dg/nint_2.f90 -O0 execution test
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: danglin at gcc dot gnu dot org
GCC build triplet: hppa*-*-hpux*
GCC host triplet: hppa*-*-hpux*
GCC target triplet: hppa*-*-hpux*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33595
next reply other threads:[~2007-09-29 21:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 21:27 danglin at gcc dot gnu dot org [this message]
2007-10-01 13:13 ` [Bug fortran/33595] " fxcoudert at gcc dot gnu dot org
2007-10-01 16:33 ` dave at hiauly1 dot hia dot nrc dot ca
2007-10-01 16:39 ` fxcoudert at gcc dot gnu dot org
2007-10-01 17:29 ` dave at hiauly1 dot hia dot nrc dot ca
2007-12-22 7:38 ` jvdelisle at gcc dot gnu dot org
2008-12-04 3:05 ` billingd at gcc dot gnu dot org
2008-12-04 5:13 ` billingd at gcc dot gnu dot org
2008-12-28 20:26 ` danglin at gcc dot gnu dot org
2008-12-28 20:41 ` dave at hiauly1 dot hia dot nrc dot ca
2008-12-28 20:47 ` danglin at gcc dot gnu dot org
2008-12-28 21:03 ` kargl at gcc dot gnu dot org
2008-12-28 21:50 ` dave at hiauly1 dot hia dot nrc dot ca
2008-12-28 22:16 ` kargl at gcc dot gnu dot org
2008-12-29 17:12 ` danglin at gcc dot gnu dot org
2009-03-28 9:41 ` fxcoudert at gcc dot gnu dot org
2009-03-28 21:16 ` danglin at gcc dot gnu dot org
2009-03-29 7:36 ` [Bug libfortran/33595] " fxcoudert at gcc dot gnu dot org
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=bug-33595-276@http.gcc.gnu.org/bugzilla/ \
--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).