This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Simulator testing for sh and sh64
- From: Kaz Kojima <kkojima at rr dot iij4u dot or dot jp>
- To: thomas at codesourcery dot com
- Cc: gcc at gcc dot gnu dot org, kevinb at redhat dot com, gdb-patches at sourceware dot org
- Date: Thu, 23 Feb 2012 08:42:53 +0900 (JST)
- Subject: Re: Simulator testing for sh and sh64
- References: <87zkca9azw.fsf@schwinge.name> <20120222093929.7e86fba2@mesquite.lan> <87wr7e8y60.fsf@schwinge.name>
Thomas Schwinge <thomas@codesourcery.com> wrote:
> This is about sh and sh64 GDB sim testing for the whole toolchain. (I
> also do have sh4a hardware available, where testing is working fine.)
> Kaz, could you please have a look whether this looks basically sane, that
> my assumptions and the results I'm getting are about right, etc.?
You are right, I think.
> Kaz, is my understanding correct, that I simply use sh64-elf as target,
> and again the sh-sim board? Should I be setting a specific CPU when
> configuring GCC, or any other customization?
I used sh64-sim board for sh64-elf. sh64-sim.exp baseboard can
be seen in
http://lists.gnu.org/archive/html/dejagnu/2008-02/msg00056.html
> This means, for sh-elf sim testing, we have a bit too many failures in
> GCC and GDB, and some ld test harness issue. For sh64-elf we have a GCC
> trunk ICE, some section overlap issue, and even more GDB issues.
Yep. About sh64, I had used sh64-linux as my testing target, but
unfortunately that real sh64 system stopped working after the earthquake.
Regards,
kaz