From: cgd@broadcom.com
To: davidu@mips.com
Cc: gdb-patches@sources.redhat.com, cagney@redhat.com
Subject: Re: MIPS32 / MIPS64 release 2 support in simulator
Date: Wed, 03 Nov 2004 16:54:00 -0000 [thread overview]
Message-ID: <yov54qk627qp.fsf@ldt-sj3-010.sj.broadcom.com> (raw)
In-Reply-To: <mailpost.1099495587.2562@news-sj1-1>
[-- Attachment #1: Type: text/plain, Size: 2748 bytes --]
Andrew (or somebody), could you please confirm that their assignment
is in place? (I don't have access to anything that would let me check
easily, as far as I know.)
At Wed, 3 Nov 2004 15:26:27 +0000 (UTC), "David Ung" wrote:
> The following file is for MIPS32 / MIPS64 release 2 extensions to the
> simulator.
Based on the way other bits are done:
* these should be placed in mips.igen proper (since they're part of a
standard MIPS ISA level). If you'd like to try dissuade me from
this position, I'm willing to discuss it. But right now, all
*other* standard MIPS ISA bits are in mips.igen itself.
* the lines like:
*mips32,mips64:
should be two separate lines.
Also:
* If you can't provide diffs for new files, at least provide them as
an attachment. (If you're interested in faking out CVS so you can
provide the diffs easily, see the attached script.) Otherwise, I
have fears about whitespace and/or line wrapping.
* If you do convince me that a new .igen file is appropriate, you'll
need to put an appropriate copyright notice and license on it.
I'd suggest starting with the one on, say, mips3d.igen.
* You need testsuite coverage for all of the new instructions, please.
* Please carefully review the instruction implementations against the
manuals, and against the defines and functions already provided by
the simulator. Right now, there are some issues.
For instance:
* DI, EI should sign extend the result, and should use
status_IE rather than '1'.
* I believe you should be using TRACE_ALU_INPUT0 in DI, EI and
in possibly similar places.
* you are missing letters in wrpgpr and rdpgpr in comment.
* in dshd, I get what you're trying to do, but the code should
be less complex to do it. (in particular, the use of the
0xffff0000 masks is confusing). Just write the code the
obvious way. 8-)
* should use check_fpu in FPU ops, and I believe you should
be using check_u64 in the 64-bit ops. Also, appropriate use
of NotWordValue would be good.
* should probably just move the ror/rorv instructions from
vr.igen into mips.igen, and use them since they are as far
as I know otherwise the same. Yes, I know they don't print
out w/ the official MIPS mnemonics, but the assembler
recognizes both and, well, uh, MIPS named them last. 8-)
There may be more, those are just the things I noticed on a quick
read-through. (Obviously, I'll have to review any updated patch.)
(We did an implementation of r2, too, but I've never had time to
submit it back. *sigh* Now *I* get to lose on the merge. 8-)
chris
[-- Attachment #2: fakeadd --]
[-- Type: application/octet-stream, Size: 666 bytes --]
#!/bin/sh
if [ $# -eq 0 ]; then
echo "usage: $0 file ..." 1>&2
exit 1
fi
if [ -d CVS ]; then :; else
echo "$0: fatal error: no CVS directory!
exit 1
fi
if [ -f CVS/Entries ] && [ -w CVS/Entries ]; then :; else
echo "$0: fatal error: CVS/Entries file not writable!
exit 1
fi
rv=0
for file in "$@"; do
if [ -f "$file" ]; then :; else
echo "$0: error: \"$file\" does not exist or is not a plain file"
rv=1
continue
fi
if grep "^/$file/" CVS/Entries > /dev/null 2>&1; then
echo "$0: error: \"$file\" is already listed in CVS/Entries"
rv=1
continue
fi
echo "/$file/0/dummy timestamp//" >> CVS/Entries
echo "$0: added \"$file\""
done
exit $rv
next prev parent reply other threads:[~2004-11-03 16:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 15:26 David Ung
[not found] ` <mailpost.1099495587.2562@news-sj1-1>
2004-11-03 16:54 ` cgd [this message]
2004-11-03 16:57 ` cgd
[not found] ` <mailpost.1099501062.5136@news-sj1-1>
2004-11-03 19:01 ` cgd
2004-11-04 13:53 ` David Ung
[not found] ` <mailpost.1099576418.9773@news-sj1-1>
2004-11-04 17:46 ` cgd
2004-11-08 16:44 ` Andrew Cagney
2004-11-08 18:06 ` David Ung
2004-11-09 15:54 ` David Ung
2004-11-09 16:12 ` Andrew Cagney
2004-11-09 16:23 ` cgd
2004-11-09 17:00 ` Andrew Cagney
2004-11-09 17:38 ` cgd
2004-11-24 17:08 ` David Ung
2004-11-24 18:17 ` cgd
2005-05-18 18:11 ` [patch ping] " David Ung
2005-05-19 2:04 ` cgd
[not found] ` <mailpost.1116450142.2303@news-sj1-1>
2005-05-25 2:21 ` cgd
2005-05-26 22:27 ` cgd
2005-05-27 14:38 ` David Ung
2004-11-09 23:36 ` Nigel Stephens
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=yov54qk627qp.fsf@ldt-sj3-010.sj.broadcom.com \
--to=cgd@broadcom.com \
--cc=cagney@redhat.com \
--cc=davidu@mips.com \
--cc=gdb-patches@sources.redhat.com \
/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