From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-433633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 30189 invoked by alias); 5 Nov 2013 16:27:17 -0000
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
Received: (qmail 27636 invoked by uid 55); 5 Nov 2013 16:25:15 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/58020] Code for handling IEEE exceptions
Date: Tue, 05 Nov 2013 16:27: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: NEW
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: <bug-58020-4-rO4YaFXjXn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58020-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58020-4@http.gcc.gnu.org/bugzilla/>
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-11/txt/msg00410.txt.bz2

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

--- Comment #19 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Nov 05, 2013 at 04:10:00PM +0000, fxcoudert at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58020
> 
> --- Comment #18 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
> (In reply to Francois-Xavier Coudert from comment #17)
> > IEEE_SUPPORT_* functions are allowed in specification expressions
> 
> On second thought, I think we can handle these on the library side (PURE
> functions in modules are allowed in specification expressions, right?)

There's a long list in F2008, 7.1.11 on what is permitted in a
specification expression.  Item (10) is

(10) a reference to any other standard intrinsic function where each
     argument is a restricted expression,

All intrinsic functions are PURE unless otherwise specifically stated
in the description of a given intrinsic function.

This differs tremendously from the short list of intrinsic functions
that were permitted by F95.