xiar error when using IPO. Fix?

xiar error when using IPO. Fix?

Portrait de henrikk
henrikk
mar, 20/03/2012 - 13:47

The steps at the end of this post will result in the xiar error:

# xiar cr libslatec.a *.o
error: can't open file /tmp/xiariEvdns_ipo/qagie.o for write
xiar: error #10014: problem during multi-file optimization compilation (code 1)

I have been able to duplicate this on seperate systems with 4GB and 64GB RAM and lots of disk space. When I change -ipo to -ip below there is no error. How do I fix this? What am I doing wrong?

- Henrik

-----

Centos 6.2
Linux ... 2.6.32-220.7.1.el6.x86_64 #1 SMP Wed Mar 7 ... x86_64 GNU/Linux
ifort version 12.1.3

-----

wget http://www.netlib.org/slatec/slatec_src.tgz
wget http://www.netlib.org/slatec/slatec4linux.tgz
tar zxf slatec_src.tgz
cd src
tar zxf ../slatec4linux.tgz

ifort -O3 -ipo -fp-model precise -c *.f
xiar cr libslatec.a *.o

RSS Haut
11 posts / 0 nouveau(x)
Dernière contribution
Reportez-vous à notre Notice d'optimisation pour plus d'informations sur les choix et l'optimisation des performances dans les produits logiciels Intel.
Portrait de Kevin Davis (Intel)
Kevin Davis (Intel)
mar, 27/03/2012 - 12:20

I will try reproducing the error and post again when I know more.

Haut
Portrait de henrikk
henrikk
mer, 28/03/2012 - 07:20

Were you able to duplicate the problem?

- Henrik

Haut
Portrait de Kevin Davis (Intel)
Kevin Davis (Intel)
mer, 28/03/2012 - 10:54

Yes, exactly. The xiar step is creating a lot of temp directories and files. It does appear to be a compiler/xiar issue and nothing tied tofile system. The file system that I am using has significant available space/i-nodes.

I will keep you updated if I am able to find a work around.

Haut
Portrait de Kevin Davis (Intel)
Kevin Davis (Intel)
jeu, 29/03/2012 - 02:02

I founda work around that Development confirmed is valid. You can avoid the error by adding smaller groups of files into the archive at one time. I found the following works:

xiar cr libslatec.a [a-m]*.o
xiar cr libslatec.a [n-z]*.o

I directed the original test case to Development for further investigation and future remedy (internal tracking id below) and will keep you updated on the status as I learn it.

(Internal tracking id: DPD200181349)

(Resolution Update on 10/14/2012): This defect is fixed in the Intel® Fortran Composer XE 2013 Initial Release (2013.0.0.079 - Linux)

Haut
Portrait de henrikk
henrikk
mer, 02/05/2012 - 08:05
So I downloaded 2011 Update 10, but the problem still apears present. Any ideas when it will be fixed? Thanks, - Henrik
Haut
Portrait de Kevin Davis (Intel)
Kevin Davis (Intel)
mer, 02/05/2012 - 08:19

I do not have an ETA on any fix yet. Development is still investigating the root cause. I will update the thread as I learn more.

Haut
Portrait de Kevin Davis (Intel)
Kevin Davis (Intel)
mar, 08/05/2012 - 14:53

The root cause has been identified and fixed. The fix will be available in our next major release scheduled for late this year. The fix will not be available for the Fortran Composer XE 2011 release, so the earlier work around will be necessary with that release.

Haut
Portrait de IanH
IanH
mar, 08/05/2012 - 16:38

"Late" or "later" this year? The number and nature of issues reported as fixed in this next major release is such that the distinction in intent between those two words has become rather material.

Haut
Portrait de Steve Lionel (Intel)
Steve Lionel (Intel)
mer, 09/05/2012 - 08:26

Third quarter of 2012.

Steve
Haut
Portrait de Kevin Davis (Intel)
Kevin Davis (Intel)
dim, 14/10/2012 - 03:07

This defect is fixed in the Intel® Fortran Composer XE 2013 Initial Release (2013.0.0.079 - Linux)

Haut

Connectez-vous pour laisser un commentaire.