<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="">Hello all,<div class=""><br class=""></div><div 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. Currently I use the default compiler flags that petsc generates for debugging support with MPICH: </div><div class=""><br class=""></div><div 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=""></div><div class="">Version: Apple clang version 11.0.0 (clang-1100.0.33.17)</div><div class=""><br class=""></div><div 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.</div><div class=""><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>
<br class=""></div></body></html>