From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11039 invoked by alias); 1 Jul 2013 10:40:42 -0000 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 Received: (qmail 11028 invoked by uid 89); 1 Jul 2013 10:40:42 -0000 X-Spam-SWARE-Status: No, score=-6.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 01 Jul 2013 10:40:41 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r61Aedb8018093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 1 Jul 2013 06:40:39 -0400 Received: from psique (ovpn-113-175.phx2.redhat.com [10.3.113.175]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r61Aeaeg019498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 1 Jul 2013 06:40:38 -0400 From: Sergio Durigan Junior To: Andreas Schwab Cc: GDB Patches Subject: Re: [PATCH 00/17] Implement gdbarch_gdb_signal_to_target References: <1372664545-3947-1-git-send-email-sergiodj@redhat.com> X-URL: http://www.redhat.com Date: Mon, 01 Jul 2013 10:40:00 -0000 In-Reply-To: (Andreas Schwab's message of "Mon, 01 Jul 2013 10:43:19 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-07/txt/msg00025.txt.bz2 On Monday, July 01 2013, Andreas Schwab wrote: > Sergio Durigan Junior writes: > >> What I did was to investigate, on the Linux kernel, which targets shared >> the signal numbers definition with x86. My approach was to make the x86 >> the "de facto" implementation, and extend only the needed bits on each >> arch. For the record, I used linux-3.10-rc6 as the main source of >> information, always looking at >> arch//include/uapi/asm/signal.h. For SIGRTMAX (which defaults >> to _NSIG in most cases), I had to look at different signal-related >> files, but most of them (except MIPS) were defined to 64 anyway. > > There is also include/uapi/asm-generic/signal.h (which happens to agree > with x86 numbering) which will be used for every new architecture port. Thanks for pointing that out. > (Looks like you missed out aarch64.) Indeed. I will submit the patch with the funny subject "[PATCH 18/17]". Thanks, -- Sergio