--- Comment #7 from fxcoudert at gcc dot gnu dot org 2007-10-24 09:42
---
(In reply to comment #6)
> FX, you confirmed this enhancement: is do-as-the-others-do really good enough
> a
> reason to implement this?
No (see http://gcc.gnu.org/ml/fortran/2007-10/msg00263.html). The SIGNAL
i
--- Comment #6 from dfranke at gcc dot gnu dot org 2007-05-29 18:13 ---
I am currently looking at the implementation of signal, so adding this may be
not too much effort. Some questions/remarks:
> The third argument "flag" is an integer that plays the role of SIG_DFL
> in the C library
--- Comment #5 from fxcoudert at gcc dot gnu dot org 2006-10-02 11:59
---
Confirmed, as Intel, Portland and other compilers accept this. Marked as an
enhancement, though, as g77 didn't support that anyway.
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed
--- Comment #4 from cummings at cacr dot caltech dot edu 2006-09-28 02:00
---
Created an attachment (id=12345)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12345&action=view)
sample code for signal intrinsic function with optional third argument
OK, here is a sample code showing
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2006-09-27 01:26
---
Can you provide a small working example of what you are trying to do?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29240
--- Comment #2 from cummings at cacr dot caltech dot edu 2006-09-26 23:32
---
Yes, I read through both the gfortran and the older g77 documentation on this
before I posted my bug report. However, I am puzzled as to why there is no
support for this third optional argument to the signal(
--- Comment #1 from kargl at gcc dot gnu dot org 2006-09-26 22:29 ---
gfortran supports an intrinsic function and an intrinsic subroutine
as defined by g77. See the g77 documentation. These routines are
provided solely for backwards compatibility with g77, and I doubt
anyone will upda
