<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote type="cite" class="">Because the code doesn't get recompiled when there are no changes.<br class=""></blockquote><div class="">Subsequent recompiles of the code with any changes also don’t reproduce the warning. The only way the warning pops up again is if I change the problematic code to correct code, compile, change it back to problematic then compile again. And then the warning only ever “stays around” for one compile.</div><br class=""><div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>Best regards,<br class=""><br class="">Jacob Faibussowitsch<br class="">(Jacob Fai - booss - oh - vitch)<br class="">Cell: (312) 694-3391</div></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Mar 23, 2020, at 11:16 AM, Satish Balay <<a href="mailto:balay@mcs.anl.gov" class="">balay@mcs.anl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Mon, 23 Mar 2020, Jacob Faibussowitsch wrote:<br class=""><br class=""><blockquote type="cite" class="">Hello all,<br class=""><br class="">I’m wondering if you guys use any extra compiler flags when debugging (other than -g3). I have noticed for example that when compiling I am only warned about something (i.e. wrong argument type for a function) once, so if I recompile the same program with no changes, the second compilation doesn’t reproduce the warning.<br class=""></blockquote><br class="">Because the code doesn't get recompiled when there are no changes.<br class=""><br class="">You can use -Werror - this will force to fix all warnings. [This is what we do in the test pipelines for some of the jobs]<br class=""><br class="">Satish<br class=""><br class=""><blockquote type="cite" class="">Currently I use the default compiler flags that petsc generates for debugging support with MPICH: <br class=""><br class="">C Compiler: /Users/jacobfaibussowitsch/NoSync/petscpackages/bin/mpicc -Wall -Wwrite-strings -Wno-strict-aliasing -Wno-unknown-pragmas -fstack-protector -fno-stack-check -Qunused-arguments -fvisibility=hidden -g3 <br class=""><br class="">Version: Apple clang version 11.0.0 (clang-1100.0.33.17)<br class=""><br class="">I’m mainly trying to find a 64-bit bug, so I have now added the “-ftrapv” flag to trap for integer overflows but there are probably more flags out there.<br class=""><br class="">Best regards,<br class=""><br class="">Jacob Faibussowitsch<br class="">(Jacob Fai - booss - oh - vitch)<br class="">Cell: (312) 694-3391<br class=""><br class=""><br class=""></blockquote></div></div></blockquote></div><br class=""></body></html>