Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’d like gcc to do source code analysis for errors, but do not write any output files (similarly to what splint does).
I’ve found this solution currently:
gcc -Wall -c source.c > NUL
Well, you could redirect the output to
/dev/null