Not built for processor error

[lhartzman]

I'm building an app that is run on a cluster of quad CPU nodes. Each CPU is a Xeon 5150 @ 2.66 GHz. If I give the combination of compiler options -O3 -xP -tpp7 -ip, the job dies with a complaint about not being built for the processor. The application is normally built with the same set of options except for -xW in place of -xP.

The bizarre thing to me is that I could build and run the app using -O3 -static -xP -tpp7. Does -xP and -ip in combination cause a problem?

Les

[TimP]

-tpp7 would be redundant with -xW or -xP, and may be meaningless with compilers which support those options. Recent compilers have some form of -ip set by default, so you may not require that option. -xO generates code similar to -xP, without the CPU identity check.

[Brandon_H_Intel]

Quoting - lhartzman

I'm building an app that is run on a cluster of quad CPU nodes. Each CPU is a Xeon 5150 @ 2.66 GHz. If I give the combination of compiler options -O3 -xP -tpp7 -ip, the job dies with a complaint about not being built for the processor. The application is normally built with the same set of options except for -xW in place of -xP.

The bizarre thing to me is that I could build and run the app using -O3 -static -xP -tpp7. Does -xP and -ip in combination cause a problem?

Les

The difference here is unexpected. Could there be a difference in whether -xP is used to compile the main() routine? I would recommend submitting an issue to Intel Premier Support on this.