Talk:Catherine Pitt

pathscale -Ofast:

I had many problems getting pathscale to compile CPMD when using the -Ofast option (whereas it was easy if I used a lower level of optimisation) and so I had to give up. I wonder if this is why...--james 17:33, 20 March 2008 (GMT)

Do you find you get a load of library not found errors? If so then this is probably the reason. I can always try to add the appropriate pieces to make Pathscale behave in to the library modules. --Catherine 11:34, 25 March 2008 (GMT)

Yup, this does seem to make a big difference! I don't think there are any modules on the workstations that require this fix. The ACML on tardis was already fixed (this is where I found the note) and I've done the new FFTW module on tardis (won't go live until I unleash a whole set of changes to make tardis's modules more logical) --Catherine 11:57, 25 March 2008 (GMT)

I think it was library not found/linking errors. I'll have to check. I'm fairly certain it was on my workstation though. I'll take a look again. --james 12:20, 25 March 2008 (GMT)

Indeed it is. On keiko:

$ make
....
/shared/shared/pathscale/pathscale-compilers-suse9.0-3.0-103.13929_suse9.0_psc/lib/3.0/ipa_link: cannot find -lacml
pathf90 INTERNAL ERROR: /shared/shared/pathscale/pathscale-compilers-suse9.0-3.0-103.13929_suse9.0_psc/lib/3.0/ipa_link returned non-zero status 1

If I replace the Ofast with O3, then it works fine. --james 13:44, 25 March 2008 (GMT)

Thanks! I need to go and mangle the ACML modules I guess (you're using one of my modules, right?) I missed them this morning because I don't have a 64-bit workstation handy for testing. --Catherine 15:14, 25 March 2008 (GMT)

I'm using the amcl/64/pathscale module. We all know whose fault the lack of a 64-bit test machine is... ;-) --james 15:49, 25 March 2008 (GMT)