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/59313] New: gfortran.dg/erf_3.F90 FAILs on Solaris/SPARC
Date: Wed, 27 Nov 2013 14:24:00 -0000	[thread overview]
Message-ID: <bug-59313-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 59313
           Summary: gfortran.dg/erf_3.F90 FAILs on Solaris/SPARC
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
              Host: sparc*-sun-solaris2.*
            Target: sparc*-sun-solaris2.*
             Build: sparc*-sun-solaris2.*

The new gfortran.dg/erf_3.F90 test FAILs on Solaris/SPARC in different ways:

* On Solaris 9, it fails to link:

FAIL: gfortran.dg/erf_3.F90  -O0  (test for excess errors)

Excess errors:
Undefined                       first referenced
 symbol                             in file
erfl                                /var/tmp//ccYCQomy.o
erfcl                               /var/tmp//ccYCQomy.o
_gfortran_erfc_scaled_r16           /var/tmp//ccYCQomy.o
frexpl                              /var/tmp//ccYCQomy.o
scalbnl                             /var/tmp//ccYCQomy.o
ld: fatal: Symbol referencing errors. No output written to ./erf_3.exe

WARNING: gfortran.dg/erf_3.F90  -O0  compilation failed to produce executable

* On Solaris 10 and 11, I get an execution failure instead:

   0.00000000000000000000000000000000000
   0.00000000000000000000000000000000000
   0.00000000000000000000000000000000000
   0.00000000000000000000000000000000000
   0.00000000000000000000000000000000000
   6167208123267181.00000000000000000000

Program aborted. Backtrace:
#0  0xFEA1A0BF

  In gdb, I find

Program received signal SIGABRT, Aborted.
[Switching to Thread 1 (LWP 1)]
0xff0da440 in _lwp_kill () from /lib/libc.so.1
(gdb) where
#0  0xff0da440 in _lwp_kill () from /lib/libc.so.1
#1  0xff083d90 in raise () from /lib/libc.so.1
#2  0xff05b59c in abort () from /lib/libc.so.1
#3  0xff21c068 in _gfortrani_sys_abort ()
    at /vol/gcc/src/hg/trunk/local/libgfortran/runtime/error.c:173
#4  0xff2b7a40 in _gfortran_abort ()
    at /vol/gcc/src/hg/trunk/local/libgfortran/intrinsics/abort.c:33
#5  0x00011318 in check (a=0.45653165863355994044362586269156961, 
    b=0.45653165863355994014668559274485783)
    at /vol/gcc/src/hg/trunk/local/gcc/testsuite/gfortran.dg/erf_3.F90:50
#6  0x0001154c in test ()
    at /vol/gcc/src/hg/trunk/local/gcc/testsuite/gfortran.dg/erf_3.F90:29
#7  0x00012390 in main (argc=1, argv=0xffbff594)
    at /vol/gcc/src/hg/trunk/local/gcc/testsuite/gfortran.dg/erf_3.F90:43
#8  0x00010cfc in _start ()

  Rainer


             reply	other threads:[~2013-11-27 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 14:24 ro at gcc dot gnu.org [this message]
2013-11-29 18:48 ` [Bug fortran/59313] " ubizjak at gmail dot com
2013-12-01 19:31 ` [Bug libfortran/59313] " ubizjak at gmail dot com
2013-12-01 20:56 ` uros at gcc dot gnu.org
2013-12-01 21:00 ` ubizjak at gmail dot com
2013-12-13 22:17 ` ebotcazou at gcc dot gnu.org
2014-02-22  8:56 ` ebotcazou at gcc dot gnu.org
2014-02-25  9:28 ` ro at gcc dot gnu.org
2014-03-24  0:33 ` danglin 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-59313-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).