public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com
To: gcc-gnats@gcc.gnu.org
Subject: fortran/6304: Failure of LAPACK test dtest on irix6.5 with -mabi=64 -O2
Date: Mon, 15 Apr 2002 01:16:00 -0000	[thread overview]
Message-ID: <20020415081200.9242.qmail@sources.redhat.com> (raw)


>Number:         6304
>Category:       fortran
>Synopsis:       Failure of LAPACK test dtest on irix6.5 with -mabi=64 -O2
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 15 01:16:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     David Billinghurst
>Release:        gcc-3.1 and gcc-3.2
>Organization:
>Environment:
mips-sgi-irix6.5
>Description:
LAPACK test dtest.out 
 core dumps with -mabi=64 -O2 
 passes with -mabi=64 -O0
This is a regression from gcc-3.0 and gcc-2.95.

The test passes with
 -mabi=64 -O0
 -mabi=n32 -O2

The problem is with file dsptrf.f.  I have been able to reduce the problem size somewhat, but the problem file is still a few hundred lines.

Expected output is:

 ap( 1) =  -4.81355444E-294
 ap( 2) =  -1.08633726E-293
 ap( 3) =  -0.948585352
 ap( 4) =   0.159305733
 ap( 5) =   0.160760447
 ap( 6) =   3.18956091E-294
 ap( 7) =  -0.258576064
 ap( 8) =  -0.806074236
 ap( 9) =  -0.14806115
 ap( 10) =   1.98569967E-293
 ap( 11) =   0.494942444
 ap( 12) =   0.432991687
 ap( 13) =  -1.65005396E-293
 ap( 14) =   1.39914842
 ap( 15) =   3.99198852E-293
 ipiv( 1) =  -2
 ipiv( 2) =  -2
 ipiv( 3) =  3
 ipiv( 4) =  4
 ipiv( 5) =  5
 info =  0

The incorrect output is:

 **** wrong ****
 ap( 1) =  -4.81355444E-294
 ap( 2) =   2.2568297
 ap( 3) =   1.97065467E+293
 ap( 4) =  -1.65986654
 ap( 5) =  -0.173388354
 ap( 6) =   2.77063428E-293
 ap( 7) =   1.88221953
 ap( 8) =  -2.23333691E-293
 ap( 9) =  -4.10223298E-294
 ap( 10) =   1.86933415E+293
 ap( 11) =  -8.42291938E-294
 ap( 12) =  -8.79851537E-295
 ap( 13) =   1.18036543E-293
 ap( 14) =  -1.43259661
 ap( 15) =  -3.11209845E-293
 ipiv( 1) =  -2
 ipiv( 2) =  -2
 ipiv( 3) =  3
 ipiv( 4) =  5
 ipiv( 5) =  5
 info =  0



>How-To-Repeat:
g77 -o bug7 -mabi=64 -O2 bug_7.f dsptrf_02.f lastuff.f
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-15  8:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15  1:16 David.Billinghurst [this message]
2002-04-21  5:49 toon
2002-04-21  7:26 Billinghurst, David (CRTS)
2002-04-23  1:47 mmitchel
2002-04-25 12:41 echristo
2002-05-02 14:12 rth
2002-05-02 18:42 Billinghurst, David (CRTS)
2002-05-13 16:34 billingd

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=20020415081200.9242.qmail@sources.redhat.com \
    --to=david.billinghurst@riotinto.com \
    --cc=gcc-gnats@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).