public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48438] New: Several gfortran tests FAIL on Tru64 UNIX
Date: Mon, 04 Apr 2011 18:56:00 -0000	[thread overview]
Message-ID: <bug-48438-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48438

           Summary: Several gfortran tests FAIL on Tru64 UNIX
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ro@gcc.gnu.org
              Host: alpha-dec-osf5.1b
            Target: alpha-dec-osf5.1b
             Build: alpha-dec-osf5.1b


As can be seen on http://gcc.gnu.org/ml/gcc-testresults/2011-04/msg00287.html,
several gfortran tests fail on Tru64 UNIX:

* Even after the latest patch and with -mieee, gfortran.dg/bessel_6.f90 with
the
  prints enabled aborts after extended output:

28 -0.484778965E-02 -0.484779058E-02    0.93E-09     -1.6115591526  F  T
29 -0.365163200E-01 -0.365163200E-01    0.00E+00     -0.0000000000  T  T
30  0.396264251E-03  0.396265183E-03   -0.93E-09    -19.7153797150  F  F
IOT/Abort trap

* FAIL: gfortran.dg/large_real_kind_2.F90  -O0  execution test

  at all optimization levels.  The tests terminate with

Floating point exception

  even with -mieee.

Program received signal SIGFPE, Arithmetic exception.
0x000003ff80293a14 in cpow () from /usr/shlib/libm.so
(gdb) where
#0  0x000003ff80293a14 in cpow () from /usr/shlib/libm.so
#1  0x000000012000992c in MAIN__ ()
    at
/vol/gcc/src/hg/gcc-4.6-branch/local/gcc/testsuite/gfortran.dg/large_real_kind_2.F90:76
#2  0x0000000120015abc in main (argc=1, argv=0x11fffe068)
    at
/vol/gcc/src/hg/gcc-4.6-branch/local/gcc/testsuite/gfortran.dg/large_real_kind_2.F90:105

  for the CTEST_POWER (0.0,5.4) call.

* FAIL: gfortran.dg/nan_7.f90  -O0  execution test

  at all optimization levels:

IOT/Abort trap

  even with -mieee

Program received signal SIGABRT, Aborted.
0x000003ff800ee3e8 in kill () from /usr/shlib/libc.so
(gdb) where
#0  0x000003ff800ee3e8 in kill () from /usr/shlib/libc.so
#1  0x000003ff80223694 in tis_lock_global () from /usr/shlib/libc.so
#2  0x000003ff80141688 in tis_raise () from /usr/shlib/libc.so
#3  0x000003ff801d4e9c in abort () from /usr/shlib/libc.so
#4  0x000003ffbffe81e8 in _gfortran_abort ()
    at /vol/gcc/src/hg/gcc-4.6-branch/local/libgfortran/intrinsics/abort.c:34
#5  0x000000012000160c in MAIN__ ()
    at
/vol/gcc/src/hg/gcc-4.6-branch/local/gcc/testsuite/gfortran.dg/nan_7.f90:14
#6  0x0000000120001688 in main (argc=1, argv=0x11fffe060)
    at
/vol/gcc/src/hg/gcc-4.6-branch/local/gcc/testsuite/gfortran.dg/nan_7.f90:15
(gdb) p k2
$1 = 0xfff80000000000000000000000000000

* FAIL: gfortran.dg/nint_2.f90  -O0  execution test

Program received signal SIGABRT, Aborted.
0x000003ff800ee3e8 in kill () from /usr/shlib/libc.so
(gdb) where
#0  0x000003ff800ee3e8 in kill () from /usr/shlib/libc.so
#1  0x000003ff80223694 in tis_lock_global () from /usr/shlib/libc.so
#2  0x000003ff80141688 in tis_raise () from /usr/shlib/libc.so
#3  0x000003ff801d4e9c in abort () from /usr/shlib/libc.so
#4  0x000003ffbffe81e8 in _gfortran_abort ()
    at /vol/gcc/src/hg/gcc-4.6-branch/local/libgfortran/intrinsics/abort.c:34
#5  0x00000001200013b4 in MAIN__ ()
    at
/vol/gcc/src/hg/gcc-4.6-branch/local/gcc/testsuite/gfortran.dg/nint_2.f90:16
#6  0x00000001200016a0 in main (argc=1, argv=0x11fffe060)
    at
/vol/gcc/src/hg/gcc-4.6-branch/local/gcc/testsuite/gfortran.dg/nint_2.f90:52

(gdb) p i1
$1 = 1
(gdb) p i2
$2 = 0

  a = nearest(0.5_8,-1.0_8)
  i2 = nint(nearest(0.5_8,-1.0_8))
  i1 = nint(a)
  if (i1 /= 0 .or. i2 /= 0) call abort

* FAIL: gfortran.dg/pr45636.f90  -O  scan-tree-dump-times forwprop2 "memset" 0

  pr45636.f90.060t.forwprop2 has two calls to __builtin_memset

* FAIL: gfortran.dg/realloc_on_assign_5.f03  -O0  execution test

  at all optimization levels:

IOT/Abort trap

Program received signal SIGABRT, Aborted.
0x000003ff800ee3e8 in kill () from /usr/shlib/libc.so
(gdb) where
#0  0x000003ff800ee3e8 in kill () from /usr/shlib/libc.so
#1  0x000003ff80223694 in tis_lock_global () from /usr/shlib/libc.so
#2  0x000003ff80141688 in tis_raise () from /usr/shlib/libc.so
#3  0x000003ff801d4e9c in abort () from /usr/shlib/libc.so
#4  0x000003ffbffe81e8 in _gfortran_abort ()
    at /vol/gcc/src/hg/gcc-4.6-branch/local/libgfortran/intrinsics/abort.c:34
#5  0x00000001200018fc in MAIN__ ()
    at
/vol/gcc/src/hg/gcc-4.6-branch/local/gcc/testsuite/gfortran.dg/realloc_on_assign_5.f03:16
#6  0x00000001200019ac in main (argc=1, argv=0x11fffe070)
    at
/vol/gcc/src/hg/gcc-4.6-branch/local/gcc/testsuite/gfortran.dg/realloc_on_assign_5.f03:18

  if (a .ne. 'x') call abort

* FAIL: gfortran.dg/guality/pr41558.f90  -O0  line 7 s == 'foo'

  and several others, seems to be the usual guality/gdb fragility


             reply	other threads:[~2011-04-04 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 18:56 ro at gcc dot gnu.org [this message]
2011-04-18 17:12 ` [Bug fortran/48438] " burnus at gcc dot gnu.org
2011-04-26 17:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-04-19 14:16 ` jb at gcc dot gnu.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-48438-4@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).