Detect Intel hyperthreading and act accordingly...
Recently I determined that lo_send actually does some of the
real-time no-no operations(free, malloc?, others?), when called,
begin working on doing all lo_send's asynchronously from the main loop.
Fix some of the goofy-ness in how uint's are converted to strings
from that snippet of ASM that I copy-n-pasted...
Copy the strings and unlock the mutex instead of blocking the main thread
while liblo performs malloc()s and free()s...
Prevent some really horrible stack corruption crashes whenever GCC compiles
with anything but -O0 on the ASM functions...