G
gil
Hi,
I'm trying to find the best way to work with compiler warnings. I'd
like to remove *all* warnings from the code, and playing around with
the warning level, I've noticed that compiling with /W3 I get warnings
that with /W4 are shown as remarks, e.g.:
warning #177: variable "Foo" was declared but never referenced
....is displayed as a "remark #177" with /W4. That doesn't fit the
definitions in Intel's help page. My questions are:
1. Why did the warning turn into a remark, is this a bug? If not, what
is the intention behind this behaviour? This doesn't include ALL
warnings, e.g.
warning #504: initial value of reference to non-const must be an
lvalue
remains a warning with /W4.
2. How come issues of conversion from "double" to "float" are
displayed only as remarks with w4? Usually they are w3 with other
compilers...?
3. Can remarks be eliminated altogether, and what is the best way (in
your opinion) to go with remarks/warnings?
Thanks,
Gil Moses.
I'm trying to find the best way to work with compiler warnings. I'd
like to remove *all* warnings from the code, and playing around with
the warning level, I've noticed that compiling with /W3 I get warnings
that with /W4 are shown as remarks, e.g.:
warning #177: variable "Foo" was declared but never referenced
....is displayed as a "remark #177" with /W4. That doesn't fit the
definitions in Intel's help page. My questions are:
1. Why did the warning turn into a remark, is this a bug? If not, what
is the intention behind this behaviour? This doesn't include ALL
warnings, e.g.
warning #504: initial value of reference to non-const must be an
lvalue
remains a warning with /W4.
2. How come issues of conversion from "double" to "float" are
displayed only as remarks with w4? Usually they are w3 with other
compilers...?
3. Can remarks be eliminated altogether, and what is the best way (in
your opinion) to go with remarks/warnings?
Thanks,
Gil Moses.