Or> What worries me is that my make command line does not cause
Or> gcc to report a warning on this line
The compiler needs special knowledge about strcpy() to know that
strcpy(x, x) is bad -- in general there's nothing wrong with a
function call like foo(x, x). Of all the compilers my tests run, only
gcc 3.4 for x86-64 produced the warning
iser_verbs.c:74: warning: statement with no effect
I guess the optimization that the compiler does of strcpy() lets it
see that strcpy(x, x) is trivial. But neither gcc 3.3 nor gcc 4.0
produces a warning for the same code.
- R.
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
