This is what I have committed as r216016
Index: gcc/testsuite/ChangeLog
===
--- gcc/testsuite/ChangeLog (revision 216014)
+++ gcc/testsuite/ChangeLog (working copy)
@@ -1,3 +1,7 @@
+2014-10-08 Dominique d'Humieres
+
+
> Patch
Patch cleaning up the testsuite (while Tobias is curing is cold :) is
pre-approved.
It comes from the last-minute wording change I suggested, I suppose.
FX
Patch:
--- ../_clean/gcc/testsuite/gfortran.dg/implicit_4.f90 2014-10-07
00:21:56.0 +0200
+++ gcc/testsuite/gfortran.dg/implicit_4.f902014-10-07 19:09:45.0
+0200
@@ -6,7 +6,7 @@ END
SUBROUTINE a
IMPLICIT REAL(b-j)
-implicit none ! { dg-error "Type IMPLICIT NONE stat
Tobias Burnus writes:
> diff --git a/gcc/testsuite/gfortran.dg/implicit_4.f90
> b/gcc/testsuite/gfortran.dg/implicit_4.f90
> index 2e871b0..9bf8d86 100644
> --- a/gcc/testsuite/gfortran.dg/implicit_4.f90
> +++ b/gcc/testsuite/gfortran.dg/implicit_4.f90
> @@ -5,13 +5,13 @@ IMPLICIT NONE ! { dg-er
Hi,
On Mon, Oct 06, 2014 at 09:20:50AM +0200, Tobias Burnus wrote:
> Committing patches when having a cold doesn't seem to work. I don't have
Having fight with cold last week, I know what you're talking about ;).
> access to the computer with SVN write permission, thus, I cannot fix it
> myself
Hi Marek, hi all,
Tobias Burnus:
> Seems that gcc/fortran/libgfortran.h part is not committed, after
> r215914 I get
> gcc/fortran/decl.c:2960:28: error: âGFC_STD_F2015â was not declared in this
> scope
Committing patches when having a cold doesn't seem to work. I don't have
access to the compu
On Thu, Oct 02, 2014 at 12:35:47AM +0200, Tobias Burnus wrote:
> Tobias Burnus wrote:
> >IMPLICIT NONE (external)
> >
> >While I have implemented is as vendor extension (-std=gnu)
>
> Ups, I forgot to include the gcc/fortran/libgfortran.h change in the patch.
> See updated attachment.
Seems that
> If you have a better suggestion for the wording …
I’d suggest “IMPLICIT NONE (TYPE) statement at %C following an IMPLICIT
statement” (and the other way around).
OK, with or without the wording change, I let you decide
FX wrote:
Build and regtested on x86-64-gnu-linux.
OK for the trunk?
Looks mostly OK, but I have one question: I don’t understand what the wording
"Type IMPLICIT NONE statement” is supposed to mean. Why “type”?
Well, I want to distinguish "IMPLICIT NONE (external)" which only
applies to proc
>> Build and regtested on x86-64-gnu-linux.
>> OK for the trunk?
Looks mostly OK, but I have one question: I don’t understand what the wording
"Type IMPLICIT NONE statement” is supposed to mean. Why “type”?
FX
Tobias Burnus wrote:
IMPLICIT NONE (external)
While I have implemented is as vendor extension (-std=gnu)
Ups, I forgot to include the gcc/fortran/libgfortran.h change in the
patch. See updated attachment.
Build and regtested on x86-64-gnu-linux.
OK for the trunk?
Tobias
2014-10-02 Tobia
I don't want to implement Fortran 90's implicit none, which is of course
already supported. However, I would like to implement as vendor extension:
IMPLICIT NONE (external)
which forces at that least an "external" or "procedure" is used or an
explicit interface available, if one tries to inv
12 matches
Mail list logo
