Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
28863 Discussions

IFX 2024.0.0 integration problem for debug

andrew_4619
Honored Contributor III
1,137 Views

This type of issue has been around for a while in various guises and I guess the root causes are varied.  Anyway a simple reproducer for the new release  that is a problem in IFX and not in IFORT. It makes debugging rather difficult in IFX. Using Microsoft Visual Studio Community 2022 (64-bit)
Version 17.0.5.

andrew_4619_0-1700573791891.png

module fred
    implicit none (type, external)
    contains
    subroutine sub1( gchar )
        character(*), intent(in) :: gchar
        print *, gchar
    end subroutine sub1
end module fred
program undef_err
    use fred, only: sub1
    implicit none (type, external)
    character(80) :: gchar
    gchar = 'Hello World'
    call sub1( gchar )
end program undef_err
1 Solution
Devorah_H_Intel
Moderator
723 Views

 This issue will be fixed in the next 2024.2 Intel Fortran Compiler release. 

View solution in original post

4 Replies
JohnNichols
Valued Contributor III
1,119 Views

Screenshot 2023-11-21 081836.png

Update to VS 2022 17.8 or install VS 2022 17.9 Preview 1  this is the 17.9. It does not work on VS 2019

 

Screenshot 2023-11-21 082603.png

andrew_4619
Honored Contributor III
1,107 Views

Interesting but this problem I suspect is not simply down to VS version it could be an interaction with a combination of integration settings within VS. These sort of problems seem to come and go. It is interesting that it works in IFORT but not IFX. A workaround for now is to use IFORT rather than updating VS which for me is a version of Russian Roulette. I  would hope someone at Intel would look at this  as a problem is never truly fixed until you fully understand the root cause. 

 

0 Kudos
Devorah_H_Intel
Moderator
1,097 Views

I can reproduce it with ifx 2024 and VS 17.7.4
Escalated it to engineering. 

0 Kudos
Devorah_H_Intel
Moderator
724 Views

 This issue will be fixed in the next 2024.2 Intel Fortran Compiler release. 

Reply