From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5187 invoked by alias); 14 Sep 2006 03:05:37 -0000 Received: (qmail 5179 invoked by uid 22791); 14 Sep 2006 03:05:36 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 14 Sep 2006 03:05:34 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1GNhXd-00088P-Dr; Wed, 13 Sep 2006 23:05:29 -0400 Date: Thu, 14 Sep 2006 03:05:00 -0000 From: Daniel Jacobowitz To: Chris Johns Cc: gdb-patches@sources.redhat.com, Eli Zaretskii Subject: Re: H8300 simulator on MinGW fails to compile. Message-ID: <20060914030529.GA31175@nevyn.them.org> Mail-Followup-To: Chris Johns , gdb-patches@sources.redhat.com, Eli Zaretskii References: <4507FA7A.70504@rtems.org> <450865A0.7070604@rtems.org> <20060913203009.GA21009@nevyn.them.org> <4508AEC7.4040803@rtems.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4508AEC7.4040803@rtems.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-09/txt/msg00074.txt.bz2 On Thu, Sep 14, 2006 at 11:22:15AM +1000, Chris Johns wrote: > Did wonder why simulator signals needed to equated to the host signals. I > am still not clear why the code is like this. No good reason. It's historical ugliness. > I see what you mean. > > The TARGET_SIGNAL_* shows up in the ppc, d10v, and arm sims. The host type > SIG* such as SIGBUS appear to be in most of the sims. > > Is the solution to change sim-signal.c to use TARGET_SIGNAL_* and then > change the effected sim files to SIM_SIG* ? I'm not entirely sure any more; it's been ages since I looked at these. I think the SIM_SIG* constants may be older than the TARGET_SIGNAL_* constants; I don't think we need both... but I really don't know. The problem is that a given int variable could hold any of the three right now. It's a righteous mess. -- Daniel Jacobowitz CodeSourcery