- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1>D:\temp\Fallo_compilador2\restricciones.f90(33): error #7986: A use associated object that has the PROTECTED attribute shall not appear in a variable definition context. [PROTREALVECT]
The mentioned error is obtained with the following piece of code in an Intel Parallel Studio XE 2017 Update 5 and Intel Parallel Studio XE 2018. I paste the code and I also attach the code and compilation results. Just to mention, the error is because of sentence "protrealvect(1)=5.d0". If I comment this one, the rest of the code works fine.
MODULE parent_module
IMPLICIT NONE
!> Private, public and public protected variables
INTEGER,PRIVATE::priv
INTEGER,PUBLIC::publ
INTEGER,PUBLIC,PROTECTED::prot
REAL(8),PUBLIC,PROTECTED::protreal
REAL(8),PUBLIC,PROTECTED,DIMENSION(1)::protrealvect
!> Submodule subroutine interface
INTERFACE
MODULE SUBROUTINE modifVariables
END SUBROUTINE modifVariables
END INTERFACE
END MODULE parent_module
!C************************************************************
!C************************************************************
SUBMODULE (parent_module) submod1
IMPLICIT NONE
CONTAINS
MODULE SUBROUTINE modifVariables
priv=-1
publ=2
prot=-3
protreal=-3.d0
protrealvect(1)=5.d0
END SUBROUTINE modifVariables
END SUBMODULE submod1
!C************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It looks like a bug in the Intel Fortran compiler, note Intel now expects you to submit an incident on all their product-related issues at their Online Service Center (OSC) which you may want to do:
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It looks like a bug in the Intel Fortran compiler, note Intel now expects you to submit an incident on all their product-related issues at their Online Service Center (OSC) which you may want to do:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you FF. I already did that. Let's wait for their response and occasionally to have it corrected in the next release.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Finally, after "only" 5 months, this bug was corrected in the 2018 update 2. I had to guess it, because despite of all my efforts Intel didn't inform me about the correction. I am pretty sure that they are too busy to pay attention to the people paying for their licenses.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, to be honest, I have to point out that at least in this case, they told me in advance that apparently the bug was going to be fixed in the second next release, and they were right. I still miss more communication though.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page