From a C++/JS benchmark

[Adam Ruppe]

> But what's the purpose of those callq? They seem to call the
> successive asm instruct

I find AT&T syntax to be almost impossible to read, but it looks
like they are comparing the instruction pointer for some reason.

call works by pushing the instruction pointer on the stack, then
jumping to the new address. By calling the next thing, you can
then pop the instruction pointer off the stack and continue on where
you left off.

I don't know why they want this though. That AT&T syntax really
messes with my brain...