Andy Polyakov 60fd574cdf 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
2005-04-03 18:53:29 +00:00
..
1999-04-29 16:04:54 +00:00
2003-12-06 11:39:37 +00:00
2004-06-20 04:16:12 +00:00
2000-02-16 13:24:06 +00:00
2005-03-30 21:38:29 +00:00
2002-11-14 11:22:01 +00:00
2003-11-28 13:10:58 +00:00
2005-03-30 13:05:57 +00:00