This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/30947] intrinsic: ALARM
- From: "dfranke at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Mar 2007 21:56:56 -0000
- Subject: [Bug fortran/30947] intrinsic: ALARM
- References: <bug-30947-13648@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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