From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28680 invoked by alias); 29 Jul 2013 22:01:53 -0000 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 Received: (qmail 28568 invoked by uid 55); 29 Jul 2013 22:01:49 -0000 From: "sgk at troutmask dot apl.washington.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/58020] Code for handling IEEE exceptions Date: Mon, 29 Jul 2013 22:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libfortran X-Bugzilla-Version: 4.8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-07/txt/msg01445.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58020 --- Comment #3 from Steve Kargl --- On Mon, Jul 29, 2013 at 09:03:53PM +0000, fkrogh#gcc at mathalacarte dot com wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58020 > > --- Comment #2 from Fred Krogh --- > 1. Hanson is willing to assign the copyright if you expect to be using this > work. There were thoughts to include this work on a SIAM website where we > think SIAM would want the copyright, but if gfortran wants to use this work it > could be posted someplace that does not require copyright. Perhaps you could > provide a link that describe how this assignment can be done. The SIAM > publication is still work in progress and the package can be noted as > copyrighted in accordance with your standards. Given your 2) below, I suspect that the code would not be used within gfortran. If the code appears on the SIAM site or some other (semi-)permanent websire, then adding a link from the gfortran wiki under "Using gfortran" may be appropriate. > 2. There are no plans to support other architectures. The problem is that gfortran works on a large selection of architectures. We cannot simply pick to support i386/x86_64 and ignore all the others. At the very least, IEEE_FEATURES should report that IEEE 754 is not supported for these lesser archs. > The Fortran standard says it is ok to *not* implement the IEEE modules, This is sort of true. > but there should be a module present on non-x86 machines that indicates > this lack of support. This is not required by the standard. > Presently there is no support and no IEEE module of any kind. Yep, which is permitted by the standard. The standard actually states: "Whether the modules are provided is processor dependent." > 3. The messy code is code I wrote, and is currently (I think) likely > to be published in the Transactions on Mathematical Software. That > code is used only in the testing code and is not used in what should > be considered the main submission. It does nothing more that give > pretty output of results. Thanks for the clarification on the messy code.