This is the mail archive of the gcc-patches@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]

Re: [PATCH] PR fortran/62245 fix INT docs.


On Sun, Aug 24, 2014 at 03:58:42PM +0000, VandeVondele  Joost wrote:
> >> +of @var{A} and whose sign is the same as the sign of @var{A}. The result
> >> +is undefined if it can not be represented as an @code{INTEGER} of the
> >> +given @code{KIND}.
> >
> >The last sentence above is not needed.  
> 
> but helpful for gfortran users ?
> 

The problem is that a similar sentence would then need to be
added to other intrinsic subroutines/functions where an actual
argument might produce a result that is out-of-range of the
representable entity.  Note, that it isn't limited to just
the conversion functions.  Consider IABS() and the asymetric
range of the INTEGERi type.

integer i
i = - huge(i) - 1
print *, iabs(i)
end

> > There is a general
> > prohibition in 13.7.1 against calling INT(A) with |A| > HUGE(1_4).
> 
> maybe you could prepare a patch to add something like that to the
> section on intrinsics?

Sure, I'll come up with a statement to be added to Sec. 8.1 of
the gfortran manual.

-- 
Steve


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