IFort module file changes even though API hasn't
- Dominant language
- Python
- Stars
- 9
- Forks
- 9
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 2
Description
IFort regenerates the module file every time it is invoked even if the interface which it represents has not. Since the file includes a time stamp this means that from Fab's point of view the file changes with every compile. This will kick off a rebuild cascade.
To be clear, Intel considers this correct behaviour although other compiler vendors and certainly this user disagree. That means this behaviour will not be changed. The new IFX compiler also behaves this way.
It may be possible to work around this behaviour by zeroing out the timestamp after compilation.
See https://stackoverflow.com/questions/20421163/why-mod-files-differ-after-every-time-i-compile-a-f-file
Contributor guide
Assessment
This issue has not been assessed yet.