[Bug fortran/90536] New: 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
Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: j.ravens.nz at gmail dot com Target Milestone: --- Created attachment 46382 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46382&action=edit 6-line

[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] Spurious (?) warning when using -Wconversion with -fno-range-check

2019-05-22 Thread j.ravens.nz at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90536 --- Comment #13 from Jonathan Ravens --- Thanks everyone for your input on this issue. I hadn't realised that it could cause such dissent. As a software developer, my major driver is to manage the users' expectations. In that respect, declarin