From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-395113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 30606 invoked by alias); 26 Jun 2012 15:08:04 -0000
Received: (qmail 30592 invoked by uid 22791); 26 Jun 2012 15:08:03 -0000
X-SWARE-Spam-Status: No, hits=-4.3 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED,TW_JR
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 26 Jun 2012 15:07:49 +0000
From: "jrt at worldlinc dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47692] Numeric inaccuracy reported in testing lapack-3.3.0 BLAS module
Date: Tue, 26 Jun 2012 15:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jrt at worldlinc dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-47692-4-xMj87QiWDk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47692-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-06/txt/msg01740.txt.bz2

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

--- Comment #17 from John T <jrt at worldlinc dot net> 2012-06-26 15:07:48 UTC ---
Thank you for reminding me to submit a follow-up. Yes, blas and lapack test
cleanly with gcc and gfortran version 4.6.3.

I have since encountered a difficulty with the Octave program involving blas. A
section of code in Octave that I think compiles the documentation fails to
recognize the values returned by calls to dlamch (?) as valid ieee754 values.
I've tried a couple of obtimization settings unsuccessfully. If I can't set
flags for dlamch and slamch to produce standard ieee754 values, this too might
be worth a bug report. suggested flags?