[Bug fortran/29471] Warn with -std=f95/f2003 when BOZ is used at invalid places

[jkrahn at nc dot rr dot com]

------- Comment #15 from jkrahn at nc dot rr dot com  2007-12-12 01:04 -------
Subject: Re:  Warn with -std=f95/f2003 when BOZ is used
 at invalid places

burnus at gcc dot gnu dot org wrote:
...
>> Maybe there should be a "-f[no-]boz-range-check" to exclude range errors just
>> for the BOZ case.
> I think -fno-range-check should be enough for both, shouldn't it?
My feeling is that BOZ range errors will occur often due to a poorly
designed spec, but that other range errors may really be bugs.
Alternatively, it might be good to a define BOZ mode flag, especially
since gfortran already supports a non-standard extension, and because
the vague standard means that there will be differences among compilers.

> 
>> F2008 draft, it re-defines B/O/Z literals, named BITS instead of BOZ.
> That part got dropped, see 13 August at:
> http://www.nag.co.uk/sc22wg5/
> 
Well, I hope that they at least update the BOZ specification.


-- 


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