From: fche@redhat.com (Frank Ch. Eigler)
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: gdb@sourceware.org, Ralf Corsepius <ralf.corsepius@rtems.org>
Subject: Re: powerpc simulator instruction question
Date: Sun, 19 Nov 2006 20:37:00 -0000 [thread overview]
Message-ID: <y0mr6vz18c0.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <455E16C5.9080600@oarcorp.com>
Joel Sherrill <joel.sherrill@oarcorp.com> writes:
> >> Is the stfiwx not implemented in the simulator? Not valid?
> > Looks unimplemented. GCC didn't generate it until 2005.
> I have no idea how to read, modify, or use ppc-instructions
> to add it. How can I find the instruction in there?
The individual instruction patterns are the lines looking like "0.31,....".
The parts before the colons describe the instruction encoding, breaking
down the bits into operand fields and opcode numbers. For example:
0.31,6.RT,11./,16./,21.83,31./:X:::Move From Machine State Register
means: bits 0..5 contain the value 31
6..10 contain the field "RT" (use the expression *rT in the body)
11..15 contain a don't care field
16..20 likewise
21..30 contains the value 83
31 contains a don't care field
*601: PPC_UNIT_IU, PPC_UNIT_IU, 1, 1, 0
*603: PPC_UNIT_SRU, PPC_UNIT_SRU, 1, 1, 0
*603e:PPC_UNIT_SRU, PPC_UNIT_SRU, 1, 1, 0
*604: PPC_UNIT_MCIU, PPC_UNIT_MCIU, 3, 3, 0
These are functional unit utilization/performance numbers.
if (IS_PROBLEM_STATE(processor))
program_interrupt(processor, cia,
privileged_instruction_program_interrupt);
else {
*rT = MSR;
check_masked_interrupts(processor);
}
This code actually implements the instruction.
- FChE
prev parent reply other threads:[~2006-11-19 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 19:53 Joel Sherrill
2006-11-17 19:57 ` Daniel Jacobowitz
2006-11-17 20:08 ` Joel Sherrill
2006-11-17 20:11 ` Daniel Jacobowitz
2006-11-17 20:45 ` Joel Sherrill
2006-11-19 20:37 ` Frank Ch. Eigler [this message]
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=y0mr6vz18c0.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=joel.sherrill@oarcorp.com \
--cc=ralf.corsepius@rtems.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