This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/29240] optional argument for signal intrinsic not supported



------- 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() function when all
other gcc-compatible compilers such as Intel ifort, PathScale pathf90, and
Portland Group pgf77 have this.  I guess I don't see how you can pass a flag to
your signal handler function without this argument.  Hopefully, someone who has
contributed to this portion of the gfortran code base will comment on this.
By the way, just to clarify, I am talking about the intrinsic function form of
signal(), not the subroutine form in which there is a third argument to contain
the result of the call to signal().


-- 


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]