From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19126 invoked by alias); 8 Mar 2007 21:57:05 -0000 Received: (qmail 19028 invoked by uid 48); 8 Mar 2007 21:56:56 -0000 Date: Thu, 08 Mar 2007 21:57:00 -0000 Message-ID: <20070308215656.19027.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/30947] intrinsic: ALARM In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dfranke at gcc dot gnu dot org" 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: 2007-03/txt/msg00641.txt.bz2 ------- Comment #5 from dfranke at gcc dot gnu dot org 2007-03-08 21:56 ------- With commits #1 to #4, the problem is only partially solved. As Brooks Moses [1] points out: "Thus, to make this work right, you'll still need to implement alarm_sub4 and alarm_sub8 library functions (along with alarm_sub_int4 and alarm_sub_int8), and have gfc_resolve_alarm_sub call the appropriate one depending on the kind of the STATUS argument. This is what the other intrinsics that use default-integer-only arguments do." [1] http://gcc.gnu.org/ml/fortran/2007-03/msg00146.html -- dfranke at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |dfranke at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2007-03-03 10:23:07 |2007-03-08 21:56:56 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30947