Make bn/asm/x86_64-gcc.c gcc4 savvy. +r is likely to be initially

introduced for a reason [like bug in initial gcc port], but proposed
=&r is treated correctly by senior 3.2, so we can assume it's safe now.
PR: 1031