From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17549 invoked by alias); 22 May 2012 13:16:46 -0000 Received: (qmail 17448 invoked by uid 22791); 22 May 2012 13:16:45 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 May 2012 13:16:32 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1SWowx-0002PQ-Ne from Maciej_Rozycki@mentor.com ; Tue, 22 May 2012 06:16:31 -0700 Received: from SVR-IES-FEM-01.mgc.mentorg.com ([137.202.0.104]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 May 2012 06:16:31 -0700 Received: from [172.30.0.105] (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.1.289.1; Tue, 22 May 2012 14:16:29 +0100 Date: Tue, 22 May 2012 13:16:00 -0000 From: "Maciej W. Rozycki" To: Pedro Alves CC: Michael Eager , "gdb-patches@sourceware.org" Subject: Re: MIPS Linux signals In-Reply-To: <4FBB67AE.5090807@redhat.com> Message-ID: References: <4FB850CA.7090701@eagerm.com> <4FBAB500.7010104@redhat.com> <4FBAB948.7000808@eagerm.com> <4FBB67AE.5090807@redhat.com> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-05/txt/msg00818.txt.bz2 On Tue, 22 May 2012, Pedro Alves wrote: > So I think that to sort all of this out, we should: > > enum target_signal => enum gdb_signal > > target_signal_from_host => gdb_signal_from_host (or gdb_signal_from_host_signal) > target_signal_to_host => gdb_signal_to_host (or gdb_signal_to_host_signal) > > gdbarch_target_signal_from_host => gdbarch_gdb_signal_from_target (or gdbarch_gdb_signal_from_target_signal) > gdbarch_target_signal_to_host => gdbarch_gdb_signal_to_target (or gdbarch_gdb_signal_to_target_signal) How about we call the context of the signal "inferior" here and therefore avoid the confusion which target is the host and which host is the target altogether? I.e.: enum target_signal => enum gdb_signal target_signal_from_host => gdb_signal_from_inferior target_signal_to_host => gdb_signal_to_inferior gdbarch_target_signal_from_host => gdbarch_gdb_signal_from_inferior gdbarch_target_signal_to_host => gdbarch_gdb_signal_to_inferior Maciej