Can someone please remind me how to report bugs in beta? (latest beta on macOS, has to do with submodules). I would happily leave it here but I seem to recall that was discouraged in the past.
You can take a look here:
Note the point about Priority Support, so you can give that a try:
- Beta Program participants will:
- have full access to the software through September 2018
- receive an email invitation to take a survey within about one month of signing up
- receive Priority Support for questions on the beta product
By the way, it will be utmost kind of you to share your MCVE on the forum also which will allow other readers to be informed of your findings.
The problem is that submodules are not able to access variables/parameters defined in the parent module. Here is the MCVE code across three files:
module a use iso_fortran_env, only : stdout => output_unit implicit none integer, parameter :: ounit = stdout end module
module b use a, only : ounit implicit none private interface module subroutine do_io(data) implicit none real, intent(in) :: data(20) end subroutine end interface end module
submodule (b) b_implementation contains module procedure do_io implicit none write(ounit,*) data(:) end procedure end submodule
Then trying to compile everything:
$ ifort -c mod_a.f90 $ ifort -c mod_b.f90 $ ifort -c submod_b.f90 submod_b.f90(6): error #6404: This name does not have a type, and must have an explicit type. [OUNIT] write(ounit,*) data(:) ----------^ compilation aborted for submod_b.f90 (code 1)
This is with the latest beta on macOS:
$ ifort --version ifort (IFORT) 19.0.0.070 20180524 Copyright (C) 1985-2018 Intel Corporation. All rights reserved.
I thought we should submit any bugs with the beta too via the Intel Online Service Center at https://supporttickets.intel.com/ ;
Instructions on how to file a ticket are available here:
Someone may correct me if I am wrong.
Thanks! I reported it through the correct channel. Apologies to Intel if I'm not supposed to post here.
Support confirmed this is a regression in Beta 19, hopefully the fix will make it into the stable release in September. Filed as bug CMPLRS-51974