--- Comment #8 from pault at gcc dot gnu dot org 2006-09-12 04:38 ---
Fixed on trunk and 4.1
Paul
--
pault at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #7 from pault at gcc dot gnu dot org 2006-09-12 04:37 ---
Subject: Bug 28890
Author: pault
Date: Tue Sep 12 04:37:09 2006
New Revision: 116871
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116871
Log:
2006-09-12 Paul Thomas <[EMAIL PROTECTED]>
PR fortran/
--- Comment #6 from paul dot richard dot thomas at cea dot fr 2006-09-11
08:15 ---
The patch did not apply cleanly to 4.1; I will take a look tonight to try to
understand why.
Paul
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28890
--- Comment #5 from pault at gcc dot gnu dot org 2006-09-11 05:03 ---
Subject: Bug 28890
Author: pault
Date: Mon Sep 11 05:02:58 2006
New Revision: 116839
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116839
Log:
2006-09-11 Paul Thomas <[EMAIL PROTECTED]>
PR fortran/
--- Comment #4 from pault at gcc dot gnu dot org 2006-09-05 19:40 ---
A patch is ready but I have not had time to post it.
Watch the list this weekend.
Paul
--
pault at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from paul dot richard dot thomas at cea dot fr 2006-08-30
13:11 ---
(In reply to comment #2)
The standard is unambiguous: A string element must be written as charr(i:i).
character(*) :: charr
.
print *, charr(i)
will always be interpreted as a call to an assumed ch
--- Comment #2 from pault at gcc dot gnu dot org 2006-08-30 04:46 ---
(In reply to comment #1)
> Confirmed: changing the substring reference to the unambiguous
> write (*,*) i, charr(i:i)
> gets rid of the problem. Apparently, vene though charr is scalar, the
> reference is bei
--- Comment #1 from pault at gcc dot gnu dot org 2006-08-29 21:26 ---
Confirmed: changing the substring reference to the unambiguous
write (*,*) i, charr(i:i)
gets rid of the problem. Apparently, vene though charr is scalar, the
reference is being interpreted as an array refere
