From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20772 invoked by alias); 26 Jun 2012 16:17:13 -0000 Received: (qmail 20755 invoked by uid 22791); 26 Jun 2012 16:17:08 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED 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 16:16:55 +0000 From: "kargl at gcc dot 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 16:17: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: kargl at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Resolution Message-ID: In-Reply-To: References: 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: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-06/txt/msg01745.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47692 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID --- Comment #18 from kargl at gcc dot gnu.org 2012-06-26 16:16:54 UTC --- (In reply to comment #17) > 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? Try -O -ffloat-store.