From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4071 invoked by alias); 5 Feb 2002 16:31:35 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 3937 invoked from network); 5 Feb 2002 16:31:28 -0000 Received: from unknown (HELO localhost.redhat.com) (24.114.26.18) by sources.redhat.com with SMTP; 5 Feb 2002 16:31:28 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id B7A5C3E56; Tue, 5 Feb 2002 11:31:27 -0500 (EST) Message-ID: <3C6008DF.5020702@cygnus.com> Date: Tue, 05 Feb 2002 08:31:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.7) Gecko/20020103 X-Accept-Language: en-us MIME-Version: 1.0 To: Ben Elliston Cc: gdb-patches@sources.redhat.com Subject: Re: SH5 simulator contribution References: <15451.47633.743434.331956@scooby.brisbane.redhat.com> <3C5F55F3.2030807@cygnus.com> <15455.24394.87381.934711@scooby.brisbane.redhat.com> <3C5F66BB.50001@cygnus.com> <15455.31263.847272.160235@scooby.brisbane.redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-02/txt/msg00117.txt.bz2 > "Andrew" == Andrew Cagney writes: > > > Andrew> The mn10300 simulator binary, contains a simulator for both > > Andrew> :model:::mn10300:mn10300: > Andrew> :model:::am33:am33: > > Andrew> Which simulator to use being selected at run time. The other two are > Andrew> v850 and MIPS (not d10v). This jells well with GDB which also supports > Andrew> those same architecture variants. > > This could certainly be done. There is only one cpu variant right now > ("sh5"). That would be very useful. This means that when you say it supports the sh2..sh4 it is through the backward compatibility of the instruction set architecture. This explains why the config tweeks only enable the simulator when sh64-elf. If I understand the sim/sh simulator correctly, it currently generates an sh-dsp sim which is backward compatible with sh2-4 (sh1?) but not with sh5. This means that the new sh5 simulator is not a drop in replacement for the existing simulator (it lacks sh-dsp). Unless the new simulator gains sh-dsp support, the sim directory will need to be configurable so that the user can select either the DSP xor the SH5 simulator. That, I suspect, is going to get messy. I think GDB should be able to assume a single SH remote-sim interface but here, I suspect, it is currently contending with two different interfaces :-( Andrew