[Bug fortran/55099] Surprising but valid 'PROCEDURE attribute conflicts with INTENT attribute' error

2019-02-01 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55099

Dominique d'Humieres  changed:

   What|Removed |Added

   Priority|P3  |P5
   Severity|normal  |enhancement

[Bug fortran/55099] Surprising but valid 'PROCEDURE attribute conflicts with INTENT attribute' error

2015-11-06 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55099

Dominique d'Humieres  changed:

   What|Removed |Added

 CC||kargl at gcc dot gnu.org

--- Comment #4 from Dominique d'Humieres  ---
Improving the message will be quite trivial once an agreement is found about
the improvement. Would the addition of "This name has not been declared as an
array or a function." be OK? Can someone find a better one?

[Bug fortran/55099] Surprising but valid 'PROCEDURE attribute conflicts with INTENT attribute' error

2015-11-06 Thread Joost.VandeVondele at mat dot ethz.ch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55099

--- Comment #5 from Joost VandeVondele  
---
(In reply to Dominique d'Humieres from comment #4)
> Improving the message will be quite trivial once an agreement is found about
> the improvement. Would the addition of "This name has not been declared as
> an array or a function." be OK? Can someone find a better one?

 ‘num_proc_2d’ has not been declared as an array or a function.

would indeed be close to what ifort provides, and I think is an improvement.

[Bug fortran/55099] Surprising but valid 'PROCEDURE attribute conflicts with INTENT attribute' error

2014-01-18 Thread dominiq at lps dot ens.fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55099

Dominique d'Humieres dominiq at lps dot ens.fr changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2014-01-18
 Ever confirmed|0   |1

--- Comment #3 from Dominique d'Humieres dominiq at lps dot ens.fr ---
Still present at r206753.


[Bug fortran/55099] Surprising but valid 'PROCEDURE attribute conflicts with INTENT attribute' error

2012-10-27 Thread burnus at gcc dot gnu.org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55099



Tobias Burnus burnus at gcc dot gnu.org changed:



   What|Removed |Added



   Keywords||diagnostic

 CC||burnus at gcc dot gnu.org

Summary|Surprising 'PROCEDURE   |Surprising but valid

   |attribute conflicts with|'PROCEDURE attribute

   |INTENT attribute' error |conflicts with INTENT

   ||attribute' error



--- Comment #1 from Tobias Burnus burnus at gcc dot gnu.org 2012-10-27 
17:29:00 UTC ---

I don't know whether you'd prefer NAG's message: Inconsistent usage of

NUM_PROC_2D. Nor I am not sure that Intel's message is much better than

gfortran's or NAG's: This name has not been declared as an array or a

function.



How about the following (which of course implies that the users didn't intent

to use an array - if they did, Intel's becomes more helpful.)



PathScale/Oracles/Open64/Crayftn have: NUM_PROC_2D has the INTENT attribute,

therefore it must not be used as an external function name.



PGI has Illegal attribute - intent specified for dummy subprogram argument

num_proc_2d


[Bug fortran/55099] Surprising but valid 'PROCEDURE attribute conflicts with INTENT attribute' error

2012-10-27 Thread Joost.VandeVondele at mat dot ethz.ch


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55099



Joost VandeVondele Joost.VandeVondele at mat dot ethz.ch changed:



   What|Removed |Added



 CC||Joost.VandeVondele at mat

   ||dot ethz.ch



--- Comment #2 from Joost VandeVondele Joost.VandeVondele at mat dot ethz.ch 
2012-10-27 17:38:34 UTC ---

(In reply to comment #1)



 How about the following (which of course implies that the users didn't intent

 to use an array - if they did, Intel's becomes more helpful.)



Indeed, I was coding this with the intent of declaring it as an array, no

doubt, passing an array is much more common than passing a procedure. Note that

intel's location is also more useful in that case. I think the usefulness of

Intel's message lies in the fact that it suggests the common cause of the

error. Even with the experience I have, I first started to look for a procedure

with the same name as the variable.