Go uses an assembly syntax completely different from everyone else. That's mighty annoying.

Where "everyone else" is at least two different syntaxes in the first place, Intel and AT&T.

You can use C files and GCC syntax in your Go project. Go will use Cgo and compile it with GCC.

Ha? Doesn't it work through the 'import "C"' and then it's just regular C?

I meant something like this, i.e. not going through C at all: http://golang.org/src/pkg/syscall/asm_freebsd_amd64.s

It looks like AT&T assembly without the %s. Not really that weird.

Oh. You mean the Plan 9 assembler... It's pretty good looking to me so I haven't really considered that an issue. I guess you're on the other side of the AT&T vs. Intel assembly fence... But just how much assembly are we writing this days anyhow? I say, just wrap it all up in Go (or C through cgo) and be done with it.

C++ does it automatically, I think this is a call for Google to spend some more time optimizing floating point workloads.