From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: <gdb@sourceware.org>
Subject: odd (inappropriate?) sparc references in sim
Date: Thu, 15 Oct 2009 13:31:00 -0000 [thread overview]
Message-ID: <4AD7233C.3010005@oarcorp.com> (raw)
Hi,
I did a grep for sparc and got some hits that
might indicate cut and paste issues:
./sh64/sh-desc.c: /* FIXME: for the sparc case we can determine
insn-endianness statically.
./sh64/sim-if.c: /* Store in a global so things like sparc32_dump_regs
can be invoked
./cris/cris-desc.c: /* FIXME: for the sparc case we can determine
insn-endianness statically.
./frv/frv.c: otherwise it may result in 0x7fffffff (sparc
compatibility) or
./frv/sim-if.c: /* Store in a global so things like sparc32_dump_regs
can be invoked
./m32r/sim-if.c: /* Store in a global so things like sparc32_dump_regs
can be invoked
./iq2000/sim-if.c: /* Store in a global so things like
sparc32_dump_regs can be invoked
I am not sure about the endianness comment but the
sparc32_dump_regs one looks incorrect.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next reply other threads:[~2009-10-15 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 13:31 Joel Sherrill [this message]
2009-10-15 14:53 ` Dave Korn
2009-10-15 15:23 ` Joel Sherrill
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=4AD7233C.3010005@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gdb@sourceware.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