- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
Since version 10 of Intel Fortran, I have compiled 32 and 64 bit versions of my code on both Windows and Linux. I have noticed that compilation for x64 platform takes muuuch longer. I typically use the default optimizations for release version. I would like to know if there are simple tips for reducing the compilation time on x64 platforms.
I do not use OpenMPI.
Simo
I do not use OpenMPI.
Simo
- Balises:
- Intel® Fortran Compiler
Lien copié
8 Réponses
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
The set of default optimizations does not remain the same for different releases. What you see may be a result of more optimizations enabled.
If you use inter-procedure optimization (IPO) you may try to reduce the compile time with -(Q)ipo_jobs option.
It's description is a part of built-in help message:
-ipo-jobs
specify the number of jobs to be executed simultaneously during the
IPO link phase
n is usually set in [1(default), 2*(number of cores)]
If you use inter-procedure optimization (IPO) you may try to reduce the compile time with -(Q)ipo_jobs
It's description is a part of built-in help message:
-ipo-jobs
specify the number of jobs to be executed simultaneously during the
IPO link phase
n is usually set in [1(default), 2*(number of cores)]
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
I have just foun similar topic below - "Slow release build with 11.0.066", http://software.intel.com/en-us/forums/showthread.php?t=63541
Check which version you are using and try to update if possible.
Alexander
Check which version you are using and try to update if possible.
Alexander
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
Simo,
Search this forum for a reply from Steve relating to this issue.
The jist of the reply was one of the versions of IVF, after addition of License, was still calling and checking for the Demo License expiration. The work a round (assuming you have a valid license) was to delete the license check .DLL files.
Sorry I cannot recall the thread or names of the dll files. However, with this information you should be able to locate this yourself.
Hint,
Use Google for searchand qualify your query with "site:software.intel.com"
If Steve reads this, he might provide you with the link.
Jim Dempsey
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
Thanks, I found the the previous post. Unfortunatelly, deleting the _libFNP.dll files did not help.
Simo
Simo
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
Are you by chance using /gen-interfaces /warn:interfaces?
If so, consider making a build configuration without the /gen-interfaces /warn:interfaces. Use that for most of your compiles then when adding code with new interface, build once witht he /gen-interfaces /warn:interfaces configuration. You only need to perform this extra work when you have added/changed code that has the potential for goofing up the interfaces.
Jim Dempsey
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
Simo,
I've got the same problem and I've resolved it. All you need to do is change your platform to x64. Fo that go to
Build>cofiguration manager>Active solution platform>New>x64.
I am assuming that you are running on win32. Ignore this if you are already running x64.
Also you might wanna see IVF vs CVF speed thread.
I've got the same problem and I've resolved it. All you need to do is change your platform to x64. Fo that go to
Build>cofiguration manager>Active solution platform>New>x64.
I am assuming that you are running on win32. Ignore this if you are already running x64.
Also you might wanna see IVF vs CVF speed thread.
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
Quoting - Alexander Chaiko (Intel)
If you use inter-procedure optimization (IPO) you may try to reduce the compile time with -(Q)ipo_jobs option.
No, the problem is the long compilation time of the fortran files.
- Marquer comme nouveau
- Marquer
- S'abonner
- Sourdine
- S'abonner au fil RSS
- Surligner
- Imprimer
- Signaler un contenu inapproprié
If you don't want to use Makefile to control optimization level by subroutine, there is still the option to set -O level by comment per subroutine. Our usual experience is that when we set -O level by subroutine for best performance, compilation time is less than half the time required at default optimization level.

Répondre
Options du sujet
- S'abonner au fil RSS
- Marquer le sujet comme nouveau
- Marquer le sujet comme lu
- Placer ce Sujet en tête de liste pour l'utilisateur actuel
- Marquer
- S'abonner
- Page imprimable