You are not logged in.
Pages: 1
Does anybody know a tool or script that takes the output of gcc and, categorizes and counts all the warning messages that were generated during compilation?
Offline
vim
Offline
IMO, it's best to fix the first few errors and recompile. Subsequent errors are likely to be caused by those anyway.
Offline
IMO, it's best to fix the first few errors and recompile. Subsequent errors are likely to be caused by those anyway.
There are no errors. Just warnings.
Offline
pauldonnelly wrote:IMO, it's best to fix the first few errors and recompile. Subsequent errors are likely to be caused by those anyway.
There are no errors. Just warnings.
Then I guess I would fix those instead.
Offline
GogglesGuy wrote:pauldonnelly wrote:IMO, it's best to fix the first few errors and recompile. Subsequent errors are likely to be caused by those anyway.
There are no errors. Just warnings.
Then I guess I would fix those instead.
Well.. that wasn't the question...
Offline
I know. But considering the volume of garbage a compiler dumps out, I can't see the benifit to organizing it. Whenever I'm debugging my code or trying to make someone else's program run, I service errors/warnings in a first broken/first fixed manner, which I believe is best.
Offline
I don't understand at all what you want to do, but I think awk can help you, no?
Offline
I know. But considering the volume of garbage a compiler dumps out, I can't see the benifit to organizing it. Whenever I'm debugging my code or trying to make someone else's program run, I service errors/warnings in a first broken/first fixed manner, which I believe is best.
Consider a number of automated build machines. I'd like a quick overview of all warnings that were generated, without having to scroll through the captured output.
Offline
Pages: 1