https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #25 from harper at msor dot vuw.ac.nz ---
I received your patch but I have no idea how to install it - I have been
using Fortran off and on since 1963 but I am not a systems programmer.
My version of gfortran is
gcc version 9.4.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #23 from harper at msor dot vuw.ac.nz ---
Given what "undefined" means in Fortran, I see no bug now.
On Fri, 3 Jun 2022, jvdelisle at gcc dot gnu.org wrote:
> Date: Fri, 3 Jun 2022 21:04:22 +
> From: jvde
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #21 from harper at msor dot vuw.ac.nz ---
I have only one problem here, and it's with the f2018 standard seeming
to contradict itself in two places that both apply to this program.
12.11.1 begins "The set of input/ou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #19 from harper at msor dot vuw.ac.nz ---
Thank you. To make the outputs from my test program testdecimal.f90 easier
to compare when using different compilers, and to clarify where a reading
error happened, I have revised the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #17 from harper at msor dot vuw.ac.nz ---
On comparing that with ifort's result I think that the only remaining bug
is that if decimal='comma' then '.' is neither a decimal symbol nor a
separator (see f201
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #16 from harper at msor dot vuw.ac.nz ---
I have now used ifort on my latest test program, which you should
already have, in the hope that it helps you. It printed this:
john@johns-laptop:~/Jfh$ ifort testiostat4.f90
Compiling
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #15 from harper at msor dot vuw.ac.nz ---
Thank you. My test program failed to distinguish some bad cases from good
cases; a revised version of the program is below. The important change
was making both elements of x be 666 just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #11 from harper at msor dot vuw.ac.nz ---
Thank you Jerry. Commas as separators with DECIMAL = 'comma' may be
trickier because commas then do the job that decimal points normally do,
and they cannot act as separators.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #8 from harper at msor dot vuw.ac.nz ---
Thank you. Unfortunately I think you found some but not all of what the
standard says about semicolons as separators. You will recall that my
original bug report had a program compiled with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473
--- Comment #3 from harper at msor dot vuw.ac.nz ---
Thank you. Of course the program did not compile with -std=f95 because
there was no decimal='point' option then. But with -std=f2003 or f2008 or
f2018, and with or without n = 999
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40196
--- Comment #13 from harper at msor dot vuw.ac.nz ---
OK
On Mon, 19 Nov 2018, marxin at gcc dot gnu.org wrote:
> Date: Mon, 19 Nov 2018 11:51:27 +
> From: marxin at gcc dot gnu.org
> To: John Harper
> Subject: [Bug fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88052
--- Comment #5 from harper at msor dot vuw.ac.nz ---
The error I found is not just violating a constraint in f2008 or above.
The same constraint with different wording is in f2003, f95 and f90.
If you want to allow any constraint violations I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82709
--- Comment #2 from harper at msor dot vuw.ac.nz ---
Apologies - I did not find bug 40196 when I was looking for possible
duplicates of my bug 82709.
On Tue, 24 Oct 2017, dominiq at lps dot ens.fr wrote:
> Date: Tue, 24 Oct 2017 23:51:55 +0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82243
--- Comment #2 from harper at msor dot vuw.ac.nz ---
Since reporting the bug yesterday I have found that the bug requires the
integer n to be a subprogram argument. If instead n is a constant, the
bad array assignment is correctly diagnosed at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79312
--- Comment #2 from harper at msor dot vuw.ac.nz ---
Another manifestation of this bug:
program emptyarray6
implicit none
logical,allocatable:: OK(:)
OK = [logical::]==[real::]
print *,OK
end program emptyarray6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61627
--- Comment #2 from harper at msor dot vuw.ac.nz ---
My diagnosis of the gfortran 4.9.0 error was misleading. Len(head1) was not 1
as
I had thought but 3, so the wrong output may have been due to the
initialization or the write statement, as the
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: harper at msor dot vuw.ac.nz
This 4-line Fortran program
character(len('xyz')):: head1(2) = (/'a','b'/)
character(3)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57871
--- Comment #5 from harper at msor dot vuw.ac.nz ---
I have now found two more oddities of type promotion but I don't claim
that these are gfortran bugs, only that the mmanual might need amending.
Oddity 1. Although -freal-4-real-8 does wha
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57871
--- Comment #4 from harper at msor dot vuw.ac.nz ---
The reason I sent that bug report is that I had read the manual and
found that -freal-4-real-16 makes the available real kinds 8, 10, 16.
The Fortran standard says selected_real_kind(1) must
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55174
--- Comment #6 from harper at msor dot vuw.ac.nz 2012-11-05 00:52:10 UTC ---
On Mon, 5 Nov 2012, John Harper wrote:
> Date: Mon, 5 Nov 2012 13:02:37 +1300 (NZDT)
> From: John Harper
> To: janus at gcc dot gnu.org
> Subje
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55174
--- Comment #5 from harper at msor dot vuw.ac.nz 2012-11-05 00:02:51 UTC ---
On Sun, 4 Nov 2012, janus at gcc dot gnu.org wrote:
> Date: Sun, 4 Nov 2012 22:23:40 +
> From: janus at gcc dot gnu.org
> To: john.har...@
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55174
--- Comment #3 from harper at msor dot vuw.ac.nz 2012-11-04 20:41:10 UTC ---
On Fri, 2 Nov 2012, janus at gcc dot gnu.org wrote:
> Date: Fri, 2 Nov 2012 10:54:50 +
> From: janus at gcc dot gnu.org
> To: john.har...@
22 matches
Mail list logo
