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,fortran] Fix PR19310 unnecessary error for overflowing results


On Fri, Jun 09, 2006 at 09:45:12PM +0100, Paul Brook wrote:
> On Friday 09 June 2006 18:19, Steve Kargl wrote:
> > On Fri, Jun 09, 2006 at 06:01:31PM +0100, Paul Brook wrote:
> > > On Friday 09 June 2006 06:47, Jerry DeLisle wrote:
> > > > + fno-range-check
> > > > + Fortran RejectNegative
> > > > + Disable range checking during compilation
> > >
> > > Why no- and RejectNegative? Seem like this should be a normal option that
> > > accepts both forms (enabled by default).
> >
> > Because range checking of gfortran's constant folding is the
> > standard, everyday, setup for gfortran.  -fno-range-check
> > disables this range checking.  It is not set/unset by any other
> > option (e.g., -Wall or -std=f95), so you don't need to be
> > able to toggle range checking back on.  -fno-range-check
> > describes exactly what the option does.  If you prefer,
> > it could be -fdisable-range-check.
> 
> I don't buy that argument. The same is true for several of the other -f 
> options (eg. -fbackslash) and we accept both forms of those.
> 

Well, your counter argument isn't too compelling.
IMHO, the handling of the other options is then broken.

-- 
Steve


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