title: Easy to read Golang assembly output?
body: <p>I'm interested in examining the x86 assembly output of the standard Go compiler to see if my code is really being converted into reasonably efficient assembly code; hopefully, by profiling and examining the assembly output, I could get a clue as to where/how I should rewrite my Go code for maximum performance. But when I examine the code using the -S flag, Go spits out a mess! I'd like two things:</p>
  
  <ol>
  <li><p>Is there a way to make the Go compiler dump the assembly output into a file, not just print it out on Terminal?</p></li>
  <li><p>Also, is there a way to make the Go compiler separate out the assembly code into separate functions, with labels? I know some functions may be inlined and hence not appear in the assembly code. What I'm seeing know is just a homogenous blob of assembly which is almost impossible to understand. </p></li>
  </ol>