From: "glame" <glchen@ict.ac.cn>
To: "linux-mips" <linux-mips@linux-mips.org>
Subject: why gcc 2.95.3 generate different result with option -mips2 and -mips3 for the same code
Date: Tue, 14 Sep 2004 17:29:59 +0800 [thread overview]
Message-ID: <20040914092941Z8224931-1530+9945@linux-mips.org> (raw)
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
next reply other threads:[~2004-09-14 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 9:29 glame [this message]
2004-09-14 12:06 ` why gcc 2.95.3 generate different result with option -mips2 and -mips3 for the same code Thiemo Seufer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040914092941Z8224931-1530+9945@linux-mips.org \
--to=glchen@ict.ac.cn \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox