- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
I am assuming that when you compile with icc you must use the icc equivalent include file. There seems to be onlyone that hasthe samename
math.h
now which should I use. The gcc one or the icc one? I would think that I should use the icc one.
Any help appreciated.
Newport_j
コピーされたリンク
4 返答(返信)
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Simply use the normal
#include
and the normal path settings, so the compiler can choose.
There is an alternative if you care to try it.
#include
and the normal path settings, so the compiler can choose.
There is an alternative
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Can you replace math.h in the include file section with mathimf.h? Just a one for ome trade?
Also, which math.h file does icc use the icc version of the gcc version?
Newport_j
Also, which math.h file does icc use the icc version of the gcc version?
Newport_j
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Yes, mathimf.h replaces math.h.
icc should search first for its own copies of standard include files such as, followed by using the path of the active g++, then possibly /usr/include/ and the like. If you make the preprocessed file, e.g. icc -E yourfile.c > yourfile.i, you should see specific paths where each section of inclusion was found.
Various linux distros have changed their interpretation on whether local directories and -I paths take precedence over system paths for include file search, so it doesn't hurt to check.
icc should search first for its own copies of standard include files such as
Various linux distros have changed their interpretation on whether local directories and -I paths take precedence over system paths for include file search, so it doesn't hurt to check.
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Yes, mathimf.h replaces math.h.
icc should search first for its own copies of standard include files such as, followed by using the path of the active g++, then possibly /usr/include/ and the like. If you make the preprocessed file, e.g. icc -E yourfile.c > yourfile.i, you should see specific paths where each section of inclusion was found.
Various linux distros have changed their interpretation on whether local directories and -I paths take precedence over system paths for include file search, so it doesn't hurt to check.
icc should search first for its own copies of standard include files such as
Various linux distros have changed their interpretation on whether local directories and -I paths take precedence over system paths for include file search, so it doesn't hurt to check.
