Clang provides -wEverything which unlike -wAll actually does turn on all warnings. Now I personally don't recommend this not all the warnings are applicable to library development ( ie warnings on unused methods ).<div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Dec 6, 2012 at 3:20 PM, Tim Tautges <span dir="ltr"><<a href="mailto:tautges@mcs.anl.gov" target="_blank">tautges@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
<br>
On 12/06/2012 01:55 PM, Vijay S. Mahadevan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Going forward, I'm going to get more militant (read almost-zero-tolerance)<br>
for warnings, at least from GCC builds.<br>
</blockquote>
<br>
Fantastic !<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We'll still probably get many Intel<br>
warnings, since we don't have anybody building natively on that compiler<br>
set.<br>
</blockquote>
<br>
I build with the Intel compilers on several systems and I can take the<br>
responsibility to fix the warnings that are produced there. I will<br>
also configure a clang build to enforce rigorous standard compliance<br>
for at least the important bits of the code.<br>
<br>
</blockquote>
<br></div>
Thanks, that will help a lot. If you only make it partway through fixing the warnings, feel free to send a dump of the compile output to the list and we can divvy them up.<br>
<br>
- tim<div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Vijay<br>
<br>
On Thu, Dec 6, 2012 at 8:24 AM, Tim Tautges <<a href="mailto:tautges@mcs.anl.gov" target="_blank">tautges@mcs.anl.gov</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
I just turned on extensive warning reporting in MOAB's gnu-based builds,<br>
and fixed a boatload of warnings in the code. The ones that are left are<br>
either because I was uncertain about whether they showed bugs (mostly the<br>
ones in FBEngine) or because of C headers I didn't want to mess with right<br>
now (findpt and related ones).<br>
<br>
Those responsible for code having remaining warnings should look at them and<br>
figure out whether they're spurious or not, and get rid of them. If you're<br>
uncertain about how to remove them, ask the list.<br>
<br>
Going forward, I'm going to get more militant (read almost-zero-tolerance)<br>
for warnings, at least from GCC builds. We'll still probably get many Intel<br>
warnings, since we don't have anybody building natively on that compiler<br>
set. But, one step at a time.<br>
<br>
One thing I haven't fixed yet is warnings in test programs. I'll assign<br>
those to somebody soon.<br>
<br>
Thanks.<br>
<br>
- tim<br>
<br>
</blockquote>
<br>
</blockquote>
<br></div></div><span class="HOEnZb"><font color="#888888">
-- <br>
==============================<u></u>==============================<u></u>====<br>
"You will keep in perfect peace him whose mind is<br>
steadfast, because he trusts in you." Isaiah 26:3<br>
<br>
Tim Tautges Argonne National Laboratory<br>
(<a href="mailto:tautges@mcs.anl.gov" target="_blank">tautges@mcs.anl.gov</a>) (telecommuting from UW-Madison)<br>
phone (gvoice): <a href="tel:%28608%29%20354-1459" value="+16083541459" target="_blank">(608) 354-1459</a> 1500 Engineering Dr.<br>
fax: <a href="tel:%28608%29%20263-4499" value="+16082634499" target="_blank">(608) 263-4499</a> Madison, WI 53706<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Robert Maynard<br>
</div>