This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] fortran/29147 -- Disable integer range checking.
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Brooks Moses <bmoses at stanford dot edu>
- Cc: fortran at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Sat, 30 Sep 2006 17:54:18 -0700
- Subject: Re: [PATCH] fortran/29147 -- Disable integer range checking.
- References: <20060929041941.GA35321@troutmask.apl.washington.edu> <451CACFB.email@example.com> <20060929053424.GA35875@troutmask.apl.washington.edu> <451D9FBE.firstname.lastname@example.org> <20060929231046.GA88456@troutmask.apl.washington.edu> <451EF7DB.email@example.com>
On Sat, Sep 30, 2006 at 04:03:55PM -0700, Brooks Moses wrote:
> Steve Kargl wrote:
> >On Fri, Sep 29, 2006 at 03:35:42PM -0700, Brooks Moses wrote:
> >>Steve Kargl wrote:
> >>>The -frange-check option is documented in invoke.texi.
> >>>Jerry implemented the option to permit Inf and NaN
> >>>to be computed (e.g., "real :: x = 1. / 0."). During
> >>>constant folding, the Inf would trigger an overflow
> >>>There is a section in gfortran.texi that describes
> >>>gfortran-specific extensions involving BOZ constants.
> >>>You may want to read this text and perhaps add a blurb
> >>>about -fno-range-check.
> >>The attached patch includes the relevant documentation changes in both
> >>locations. I've tested it on both PDF and HTML document generation.
> >Thanks. The patch looks good to me. I'll commit
> >it tonight or tomorrow.
> It occurs to me that you'll want a changelog entry when you do:
> 2006-09-30 Brooks Moses <firstname.lastname@example.org>
> * invoke.texi: Add mention of BOZ constants and integer
> overflow to -fno-range-check.
> * gfortran.texi: Add mention of -fno-range-check to
> section on BOZ contants.
Committed. I'll look over your other patches after college
football and dinner.