Compiler-specific flags without checking for compiler

[joseph.schuchart@…]

Hi all,

I am building OMC (make omc) using the Intel compiler. It works fine but the Intel compiler issues warnings about the following flags that it does not understand:

icc: command line warning #10006: ignoring unknown option '-fno-tree-ch'
icc: command line warning #10006: ignoring unknown option '-fno-tree-vrp'
icc: command line warning #10006: ignoring unknown option '-fno-tree-pre'

They are added in configure.in to circumvent a GCC bug. However, they are added unconditionally and independently of the type of compiler being used.

Additionally, the following flags are used in the 3rdParty/Ipopt-3.11.6/ThirdParty/Mumps package.

ifort: command line remark #10148: option '-cm' not supported
ifort: command line remark #10148: option '-w90' not supported
ifort: command line remark #10148: option '-w95' not supported

I'm not sure where they are added.

I suggest that adding compiler-specific flags is guarded by a check for the compiler vendor and version to prevent these warnings (and possible build failures with other compilers).

[Martin Sjölund]

The flags for ipopt are set by the ipopt package, and not something we change (it is also optional).

The -fno-tree-ch/vrp/pre are only added if the compiler reports that it supports them. (icc -Werror -fno-tree-ch returns success, so -fno-tree-ch is not a warning).

[Joseph Schuchart]

I wasn't aware of the checks to ensure successful compilation. Thanks for the clarification.

[Dietmar Winkler]

Sorting away the closed as invalid, won't fix and duplicate tickets from Future.