Warning messages -warn iterfaces interpreted as errors
This is a serious error. If the compiler were to go ahead, any code produced by interprocedural analysis would probably be broken. Even with correct compilation of individual subroutines, you couldn't...
View ArticleWarning messages -warn iterfaces interpreted as errors
Tim,Do you mean this is a serious error in the compiler.In my code I made this error on purpose here and it is indeed a serious error (-warn interfaces flags this as it should). There are more errors I...
View ArticleWarning messages -warn iterfaces interpreted as errors
I admit that it is a bit confusing that we have collected various categories of compile-time diagnostics under -warn, but not all of these are strictly warnings. For example, "-warn declarations" is...
View ArticleDear all,
Dear all,in this message (Wed, 03/23/2011 - 07:08):Quote:Steve Lionel (Intel) wrote:I admit that it is a bit confusing that we have collected various categories of compile-time diagnostics under -warn,...
View ArticleInteresting - I was sure that
Interesting - I was sure that we used to make this an error. You can also add "-warn errors" to turn all warnings into errors. Or you can make this specific warning an error with "-diag-error 6717".
View ArticleAs I said above, I can't use
As I said above, I can't use "-warn errors" because I have other "safe" warnings.I wasn't aware of the option "-diag-error". It works with ifort 13.1.1, i.e. "-warn declarations -diag-error 6717" turns...
View ArticleWell, the option "-diag-error
Well, the option "-diag-error" exists in 11.1 (it is recognized on the command line), but it does not seem to work...For future ifort releases, isn't it possible to make the option "-implicitnone" act...
View ArticleIn current releases, you can
In current releases, you can get exactly the behavior you want with -diag-error 6717 and -warn declarations. No need for yet another option.
View Article-implicitnone would not be a
-implicitnone would not be a new option, it already exists. My suggestion was to make it equivalent to "-warn declarations -diag-error 6717", since I believe it is more natural given its name.
View Article