I absolutely agree with “developers need to pay attention to build flags”. Like the well-known -D_GLIBCXX_ASSERTIONS and -fasynchronous-unwind-tables. Only applicable, of course, when using GCC. I mean only when using GCC when this article was written. Only on Linux. With glibc. Did I mention only RedHat Enterprise? (AMD64?) (C or C++?)
For those of us C programmers writing for anything other than the intersection of the above, please, please, please “pay attention to” -W, -Wall, and if you’re feeling bold, -Wextra. (And everybody’s friend, -g.) Depending upon obscure GCC or Clang flags only muddies the waters—as if we need more difficulties keeping C software portable between Linux, BSD, and Mac OS X. (I don’t have the courage to write “Windows” here.)
Maybe the author should clarify to “HPC on Linux developers” or “kernel developers”? Or more practically, “RedHat Enterprise developers”?
I absolutely agree with “developers need to pay attention to build flags”. Like the well-known -D_GLIBCXX_ASSERTIONS and -fasynchronous-unwind-tables. Only applicable, of course, when using GCC. I mean only when using GCC when this article was written. Only on Linux. With glibc. Did I mention only RedHat Enterprise? (AMD64?) (C or C++?)
For those of us C programmers writing for anything other than the intersection of the above, please, please, please “pay attention to” -W, -Wall, and if you’re feeling bold, -Wextra. (And everybody’s friend, -g.) Depending upon obscure GCC or Clang flags only muddies the waters—as if we need more difficulties keeping C software portable between Linux, BSD, and Mac OS X. (I don’t have the courage to write “Windows” here.)
Maybe the author should clarify to “HPC on Linux developers” or “kernel developers”? Or more practically, “RedHat Enterprise developers”?
I also almost always use
-pedantic, too.