Richard Henderson wrote:
I do not see the point why you should discourage the register allocator
from using mmx registers, move through memory is clearly inefficent and
enlarges resulting code (if the function containing moves is inlined in
several places, even more so).
First, what you
I filed a bug #23660:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23660
Regards,
Vahur
Richard Guenther wrote:
On 8/31/05, Vahur Sinijärv <[EMAIL PROTECTED]> wrote> Hi,
No, the problem I wrote about is not fixed. I used GCC from CVS head
30.08.2005.
I think you found a different
prevents moves directly from general registers to MMX registers, so this
cannot be the case.
Regards,
Vahur
Prakash Punnoor wrote:
Hi,
Vahur Sinijärv schrieb:
I've found that latest GCC versions (past 4.0.0 and up to latest in CVS
head) never use 'movd %genreg, %mmxreg&#x
Hi !
I've found that latest GCC versions (past 4.0.0 and up to latest in CVS
head) never use 'movd %genreg, %mmxreg' to load mmx registers and always
insists doing it through memory eq.
'mov %genreg, (mem)'
'movd (mem), %mmxreg'
Older GCC versions do the same thing directly, without involving
