This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/61002] Can't divide by 0
- From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 03 May 2014 01:19:13 +0000
- Subject: [Bug fortran/61002] Can't divide by 0
- Auto-submitted: auto-generated
- References: <bug-61002-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61002
--- Comment #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Fri, May 02, 2014 at 02:24:40PM +0000, dominiq at lps dot ens.fr wrote:
>
> What is the best way to avoid the misleading "This check can be disabled with
> the option -fno-range-check" for integers? Use "This check can be disabled for
> floating point values with the option -fno-range-check"? or pass an extra
> argument to gfc_arith_error?
>
> While I am at it, should I do the same thing for "Arithmetic overflow" and
> friends? Should not "This check can be disabled with the option
> -fno-range-check" ends with a dot?
Traditional error messages did not end with punctuation. When
error messages started to be more than a sentence, we needed
to punctuate the first sentence(s), and the last sentence was
left unpunctuated.
Instead of "This check ... ". Simply use "See -fno-range-check".
Then gfortran.info can add a lengthy description about what
-fno-range-check does.