Linux MIPS Architecture development
 help / color / mirror / Atom feed
* why gcc 2.95.3  generate different result with option -mips2 and -mips3 for the same code
@ 2004-09-14  9:29 glame
  2004-09-14 12:06 ` Thiemo Seufer
  0 siblings, 1 reply; 2+ messages in thread
From: glame @ 2004-09-14  9:29 UTC (permalink / raw)
  To: linux-mips

hi,
when i disassemble the code, the result is as the following

-ffffffff80010b8c:  01001021    move    $v0,$t0  (-mips2)
+ffffffff80010b8c:  0100102d    move    $v0,$t0  (-mips3)

why? 


best regards
        glame
        

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: why gcc 2.95.3  generate different result with option -mips2 and -mips3 for the same code
  2004-09-14  9:29 why gcc 2.95.3 generate different result with option -mips2 and -mips3 for the same code glame
@ 2004-09-14 12:06 ` Thiemo Seufer
  0 siblings, 0 replies; 2+ messages in thread
From: Thiemo Seufer @ 2004-09-14 12:06 UTC (permalink / raw)
  To: glame; +Cc: linux-mips

glame wrote:
> hi,
> when i disassemble the code, the result is as the following
> 
> -ffffffff80010b8c:  01001021    move    $v0,$t0  (-mips2)
> +ffffffff80010b8c:  0100102d    move    $v0,$t0  (-mips3)
> 
> why? 

Because you told it to do so. :-)
The 32bit move is "addu v0, $0, t0", the 64bit move "daddu ...".


Thiemo

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-09-14 12:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-14  9:29 why gcc 2.95.3 generate different result with option -mips2 and -mips3 for the same code glame
2004-09-14 12:06 ` Thiemo Seufer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox