From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1947 invoked by alias); 20 Dec 2007 17:22:06 -0000 Received: (qmail 1938 invoked by uid 22791); 20 Dec 2007 17:22:05 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 20 Dec 2007 17:21:59 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id F167F98151; Thu, 20 Dec 2007 17:21:57 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id D674998150; Thu, 20 Dec 2007 17:21:57 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1J5P5p-00052K-0x; Thu, 20 Dec 2007 12:21:57 -0500 Date: Thu, 20 Dec 2007 19:37:00 -0000 From: Daniel Jacobowitz To: "Maciej W. Rozycki" Cc: gdb-patches@sourceware.org, David Ung , "Maciej W. Rozycki" Subject: Re: mips-tdep.c: Sign-extend pointers for n32 Message-ID: <20071220172156.GD17663@caradoc.them.org> Mail-Followup-To: "Maciej W. Rozycki" , gdb-patches@sourceware.org, David Ung , "Maciej W. Rozycki" References: <20071216184625.GA22905@caradoc.them.org> <20071219152826.GA30488@caradoc.them.org> <20071219161552.GA1280@caradoc.them.org> <20071220165805.GB17663@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes 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: 2007-12/txt/msg00350.txt.bz2 On Thu, Dec 20, 2007 at 05:07:42PM +0000, Maciej W. Rozycki wrote: > Hmm, these are obviously C-style types and I would expect other languages > to have their own specific ones (Ada, anyone?). As they map somehow to > the integer types provided by the underlying architecture, wouldn't it be > a good idea to actually record which of the plain CPU-specific types each > of the language types corresponds to? Yes, that sounds like a good solution. I don't think we need to fix it today, though :-) -- Daniel Jacobowitz CodeSourcery