[Bug fortran/90536] Use of -fno-range-check creates warnings or errors when assigning to a byte variable

2019-05-19 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90536 Thomas Koenig changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/90536] Use of -fno-range-check creates warnings or errors when assigning to a byte variable

2019-05-19 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90536 --- Comment #2 from Thomas Koenig --- Hm, another question: Which gfortran version do you use? If your version is _really_ old, it might not yet have the -Wno-conversion flag.

[Bug fortran/90536] Use of -fno-range-check creates warnings or errors when assigning to a byte variable

2019-05-19 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90536 --- Comment #3 from Dominique d'Humieres --- To make the story short: compile your code with -Wno-conversion as a work around. This is needed starting with at least 4.6.0 revision r161462 (2010-06-27), but not needed with 4.5.4 or earlier. Note

[Bug fortran/90536] Use of -fno-range-check creates warnings or errors when assigning to a byte variable

2019-05-19 Thread j.ravens.nz at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90536 --- Comment #4 from Jonathan Ravens --- (In reply to Thomas Koenig from comment #2) > Hm, another question: Which gfortran version do you use? > If your version is _really_ old, it might not yet have > the -Wno-conversion flag. "gfortran -v" giv

[Bug fortran/90536] Use of -fno-range-check creates warnings or errors when assigning to a byte variable

2019-05-19 Thread j.ravens.nz at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90536 --- Comment #5 from Jonathan Ravens --- (In reply to Dominique d'Humieres from comment #3) > To make the story short: compile your code with -Wno-conversion as a work > around. > > This is needed starting with at least 4.6.0 revision r161462 (20

[Bug fortran/90536] Use of -fno-range-check creates warnings or errors when assigning to a byte variable

2019-05-19 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90536 kargl at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug fortran/90536] Use of -fno-range-check creates warnings or errors when assigning to a byte variable

2019-05-19 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90536 Thomas Koenig changed: What|Removed |Added Status|RESOLVED|NEW Resolution|WONTFIX

[Bug fortran/90536] Use of -fno-range-check creates warnings or errors when assigning to a byte variable

2019-05-19 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90536 --- Comment #8 from Steve Kargl --- On Mon, May 20, 2019 at 05:24:42AM +, tkoenig at gcc dot gnu.org wrote: > Hi Steve, > > the same thing also happens if the variables are declared as > integer(kind=1), as I found yesterday, also on assignm

[Bug fortran/90536] Use of -fno-range-check creates warnings or errors when assigning to a byte variable

2019-05-20 Thread tkoenig at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90536 --- Comment #9 from Thomas Koenig --- Hi Steve, what I meant is that Program main Integer(kind=1) :: n n = 1 End should not warn with -fno-range-check -Wall, and it does.