Re: [Users] -xHost in edison.cfg

2016-09-18 Thread Erik Schnetter
On Sun, Sep 18, 2016 at 4:24 PM, Roland Haas wrote: > Hello Erik, > > > It's strange that code without "-xHost" does not run on the head node. > What > > other compiler options are there? The only reason I can see is that the > > Intel compiler has been installed in a special way to use additiona

Re: [Users] -xHost in edison.cfg

2016-09-18 Thread Roland Haas
Hello Erik, > It's strange that code without "-xHost" does not run on the head node. What > other compiler options are there? The only reason I can see is that the > Intel compiler has been installed in a special way to use additional > compiler flags, and these flags make the code not work any mo

Re: [Users] -xHost in edison.cfg

2016-09-18 Thread Erik Schnetter
It's strange that code without "-xHost" does not run on the head node. What other compiler options are there? The only reason I can see is that the Intel compiler has been installed in a special way to use additional compiler flags, and these flags make the code not work any more on Sandy Bridge.

[Users] -xHost in edison.cfg

2016-09-18 Thread Roland Haas
Hello all, NERSC's edison cluster specifies -xHost in its cfg file. However login nodes and compute nodes are actually different (Sandy Bridge vs. Ivy Bridge cpus). A quick test removing -xHost reveals a possible reason: without -xHost the compiled exectuables do not run on the head node. No for