From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13555 invoked by alias); 17 Jul 2014 16:41:30 -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 13532 invoked by uid 89); 17 Jul 2014 16:41:30 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 17 Jul 2014 16:41:29 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s6HGfO8d014831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 17 Jul 2014 12:41:25 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s6HGfLm6007106; Thu, 17 Jul 2014 12:41:22 -0400 Message-ID: <53C7FCB1.4060904@redhat.com> Date: Thu, 17 Jul 2014 16:42:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Gary Benson , gdb-patches@sourceware.org CC: Tom Tromey , Doug Evans Subject: Re: [PATCH 03/15 v2] Make gdbserver CORE_ADDR unsigned References: <1405520243-17282-1-git-send-email-gbenson@redhat.com> <1405520243-17282-4-git-send-email-gbenson@redhat.com> In-Reply-To: <1405520243-17282-4-git-send-email-gbenson@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-07/txt/msg00476.txt.bz2 The only issue that I think might come out of this is that on MIPS, addresses are signed, so pointers are sign extended. But we can definitely handle whatever fallout this may cause, if any, when we see it. Clearly if GDB's native targets can handle that, so should gdbserver's, and in any case the issue should be pretty localized. Just pointing it out FYI, to keep an eye out for it. -- Pedro Alves