<p>What are some best practices for general purpose -gcflags to use for debugging and conversely for optimizing code?</p>
<hr/>**评论：**<br/><br/>nilium: <pre><p>Are you trying to do something specific? Go doesn't really have the massive ton of flags that compilers like gcc have, so there's not really any tuning you'll be doing, if that's what you're looking for.</p>
<p>The only extra flag that's really useful in debugging, for me, is <code>-race</code> (to go install) since you don't want to overlook data races. Beyond that, the flag to print inlining decisions is handy. There are also GODEBUG values, but I don't need them very often.</p></pre>NeverUse-YouPromised: <pre><p>You can disable bounds checking with <code>-gcflags="-B"</code>.</p>
<p>With <code>-ldflags="-w -s"</code> you can achieve <code>strip</code>'s effects from the compiler.</p></pre>
